Skip to main content
Skip table of contents

"Confluence Stopped Responding" Error While Saving a Version

This troubleshooting article provides step-by-step guidance for how to troubleshoot the error message: "Confluence stopped responding.”


When attempting to save a version, you may receive an error report with the following error message:

Confluence stopped responding

You might also see a specific page mentioned along with the error, such as in this example:

Confluence stopped responding ((V1) Getting Started)

Possible Causes

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

Confluence sometimes faces difficulties when copying pages with many or heavy attachments. Unfortunately, we don't have any numbers regarding the maximum amount or file size that causes the problem. To clarify, when Scroll Documents saves a version, it relies on Confluence to copy pages, content, and attachments from the Working version. However, if Confluence fails to copy a page due to its attachments, this can lead to the save version process in Scroll Documents failing.


To troubleshoot this you should first confirm if:

  1. The issue is related to attachments

  2. The issue is limited to Scroll Documents

To confirm whether the issue is related to attachments, follow the steps below:

  1. Download and open the error report you received when you tried saving the version.

  2. Look for the error message Confluence stopped responding and check if a specific page is listed, such as: ((V1) Getting Started)

  3. Navigate to the listed page in the page tree of your Working version.

  4. Click on More actions (•••) > select Attachments > Files.

If the page has multiple or large attachments, this could be the reason for the save version action failure. Now it’s time to confirm wether the issue is related to Scroll Documents.

Follow the steps below to confirm if this issue is related to Scroll Documents:

  1. Navigate back to the reported Confluence page.

  2. Click on More actions (•••) > select Copy.

  3. Try to only copy this one page without its children, click Copy.

  4. Observe if the copy page action fails or not.

If the copy page action fails

If the copy page action also fails, this means that Confluence is unable to copy the page along with its attachments, leading to the save version action failure in Scroll Documents. In this case, we recommend reaching out to Atlassian support. Provide a description of the issue and the troubleshooting steps taken. Atlassian support will further investigate and assist you.

If the copy page action succeeds

If the copy page action succeeds, this suggests that the issue might be related to Scroll Documents. Don't hesitate to contact our support team for further assistance at

Prevention Tips

To avoid attachment-related issues when saving versions, consider the following tips:

  1. Remove attachments you no longer need from both the editor and the Attachments section of the page. You can find the Attachment section of a page by clicking on More actions (•••) > Attachments > Files.

  2. Minimize the file size before adding attachments to a Confluence page.

  3. Avoid keeping multiple attachments on the same page.

  4. Create a separate page tree outside your document and use it as an include library. Include the content into your document using Include Page macros.

See Also

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.