Troubleshooting

Sometimes, errors occur when saving versions in Scroll Documents, resulting in incomplete page trees.

When creating a new Scroll Document, choose to enable it on a single page, a subset, or the entire space page tree. This article helps identify and resolve issues with enabling Scroll Documents.

This issue can occur if there is a page in your Scroll Document's Working version that contains numerous attachments.

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.

If the error message "Broken reference" appears, it may indicate that the root page of your version has been deleted.

If the document have been moved to a restricted or deleted space this can lead to the error message “Document not found”.

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.

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."

Not all dynamic macros can always be displayed as expected.

You want to delete a migrated document and are encountering the error: No permission to delete some items in the page tree.

When adding a Scroll Document to your Viewport site, you face the error: Content source could not be found.

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.