Troubleshooting
Saving a Version and Publishing Issues
- Incomplete Page Tree After Saving a Version Fails — Sometimes, errors occur when saving versions in Scroll Documents, resulting in incomplete page trees.
- Resolve "Page with id XXXX is part of a nested document" — Scroll Documents does not support nesting page trees from different documents within each other. This article explains how to identify and resolve this issue.
- "Confluence Stopped Responding" Error While Saving a Version — This issue can occur if there is a page in your Scroll Document's Working version that contains numerous attachments.
- Resolve "Version Location Not Found"/ "Version Location Permission Missing" — The version location page serves as the parent page where your saved versions are added. To save a version, you must have view and edit access to this page.
- Unable To Add a Document to Viewport — When adding a Scroll Document to your Viewport site, you face the error: Content source could not be found.
Page Group and Scroll Page ID Issues
- Missing Scroll Page ID — This article explains how to find pages that are missing a Scroll Page ID and how to add one.
- Duplicate Scroll Page IDs — This article explains how to find and fix pages that have duplicate Scroll Page IDs.
- Page Assigned To Wrong Page Group — This article explains how to find and fix pages that have been assigned to the wrong Page Group.
Document and Page Tree Issues
- Resolve "Document Not Found" — If the document have been moved to a restricted or deleted space this can lead to the error message “Document not found”.
- Resolve "Broken Document Link — The document version associated with the page tree may have been deleted by a user who had access to the document, but not to this particular page tree.
- Resolve "Broken Reference" — If the error message "Broken reference" appears, it may indicate that the root page of your version has been deleted.
- Inconsistent Page Tree Order — If you notice inconsistencies in the page tree order within your Scroll Documents-managed spaces, this article explains the potential cause and provides a workaround.
Content Display Issues
- Dynamic Macros Aren't Displayed as Expected — Not all dynamic macros can always be displayed as expected.
- Broken Attachment References on Pages — In some cases, after saving a version or translating a page, you may encounter broken attachment references. Instead of displaying the preview of the attachments, you will see a message saying "Preview unavailable."