Troubleshooting

You cannot create a document in a space where the legacy apps Scroll Versions and Scroll Translations are already active.

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.

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.

Saving a version, publishing to Confluence, and creating a translation all copy or update pages in your document. If you can't edit some of these pages, Scroll Content Manager lists them so you can fix their restrictions in one go.

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.

Not all dynamic macros can always be displayed as expected.