Notion Import: Pages may fail to open with "Something went wrong on our end" due to attachment rendering error

XMLWordPrintable

    • 1
    • Minor

      Issue Summary

      • Pges imported from Notion into Confluence Cloud may be inaccessible and display a "Something went wrong on our end" error. Investigation reveals a RuntimeException during XHTML storage transformation caused by a null attachment resource identifier.

      Steps to Reproduce

      1. Perform an import from Notion to Confluence Cloud.
      2. Navigate to the newly created space and attempt to open an imported page that contains attachments.
      3. Observe the error message on the page UI.

      Expected Results

      • Imported pages should open successfully, correctly rendering all content including attachments.

      Actual Results

      • The page fails to load, showing a "Something went wrong on our end" message and throwing a RuntimeException in the backend logs related to AttachmentResourceIdentifier.

      Workaround

      • Currently, there is no known workaround for this behavior. A workaround will be added here when available.

              Assignee:
              Raman Samoilenka
              Reporter:
              Avrahm K [Atlassian Support]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: