-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Page - Content
-
2
-
Severity 3 - Minor
Issue Summary
Multiple pages are not loading in customer's env and we keep getting the following error:
We’ve hit a snag
The issue should resolve on its own, but if it keeps happening, ask your admin to contact our support team and give them:
- The URL of this page
- The code associated with this error: qo6777
Refresh page
This is reproducible on Data Center: no
Steps to Reproduce
- Login to customer's site.
- Navigate to any page in question.
Expected Results
- Page loads successfully.
Actual Results
- We run into the error "We’ve hit a snag"
- We can see following errors on splunk:
{ [-] ctx: { [+] } ec2: { [+] } env: prod-euwest ext: { [-] accessStatus: LICENSED_ADMIN_ACCESS accountId: 639985b876fb74a9514265ff analytics: true confluenceVersion: 1000.0.0-09a08239c208 connection: 732c1588 event: { [-] appAccess: atlPath: null atlassianAccountId: 639985b876fb74a9514265ff clientTime: 1702040099943 name: confluence.fabric.editor.unsupported.content product: confluence properties: { [-] ancestors: Expected ac:emoticon end element but got: * : com.atlassian.confluence.content.render.xhtml.atlassiandocformat.adf.AbstractXhtmlToADFFragmentTransformer.consumeEndElement(AbstractXhtmlToADFFragmentTransformer.java:168) | com.atlassian.confluence.content.render.xhtml.atlassiandocformat.adf.EmojiXhtmlToADFFragmentTransformer.doTransformFragment(EmojiXhtmlToADFFragmentTransformer.java:86) | com.atlassian.confluence.content.render.xhtml.atlassiandocformat.adf.AbstractXhtmlToADFFragmentTransformer.transformFragment(AbstractXhtmlToADFFragmentTransformer.java:73) | com.atlassian.confluence.content.render.xhtml.atlassiandocformat.adf.DefaultXhtmlToADFFragmentTransformer.transformFragment(DefaultXhtmlToADFFragmentTransformer.java:59) | com.atlassian.confluence.content.render.xhtml.atlassiandocformat.adf.PlainXhtmlToADFFragmentTransformer.doTransformFragment(PlainXhtmlToADFFragmentTransformer.java:150) category: EXCEPTION contentId: 226596093953 contentStatus: current contentType: page descendants: fabricPage: true meta: nodeType: Expected ac:emoticon end element but got: * scanId: siblings: templateId: 0 } receivedTime: 1702040099943 requestCorrelationId: 4da11bf26a7b4014b244ca9c0c69efe8 sen: SEN-15056440 server: sophos.atlassian.net session: null sourceIp: 54.255.101.113 subProduct: analytics user: masked.user version: 1000.0.0-09a08239c208 } experience: unknown op: Bulk_PaginatedSmartLinkList/contentSmartLinks route: READER traceId: 4da11bf26a7b4014b244ca9c0c69efe8 } hostname: 3cc1633d3894 level: INFO logger: com.atlassian.analytics.event.transport.LaasEventTransport m: { [-] di: r9hus144mtdb748j g: WebServer si: confluence-prod-eu-12 sv: 2023-12-07-23-29-01-317995_2023-12-07_09a08239c2 t: application } message: Analytics event micros_container: confluence product: confluence thread: workcontext-8387682-0 time: 2023-12-08T12:54:59.945659625Z timestamp: 2023-12-08T12:54:59.944 }
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available