Troubleshooting

When creating a new document, choose to create it on a single page, a subset, or the entire space page tree. This article helps identify and resolve issues with creating a document.

Sometimes, errors occur when saving versions of a document, resulting in incomplete page trees.

Scroll Content Manager does not support nesting page trees from different documents within each other. This article explains how to identify and resolve this issue.

This issue can occur if there is a page in your 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.

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

This article explains how to find pages that are missing a Scroll Page ID and how to add one.

This article explains how to find and fix pages that have duplicate Scroll Page IDs.

This article explains how to find and fix pages that have been assigned to the wrong Page Group.

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.

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

If you notice inconsistencies in the page tree order within your document this article explains the potential cause and provides a workaround.

Not all dynamic macros can always be displayed as expected.

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

If all Scroll Apps are not pinned to the same Data Residency region, this can cause issues with the app licenses.