In this page

Frequent problems and solutions

Jobs and content processing

The job execution log contains paging errors for some spaces.

When the app processes content in a space, it runs CQL queries against the Atlassian REST API and iterates through the results page by page. In some cases, the API returns an unexpected error code for the first page of results or for a subsequent page, causing the job to log an error and fail.

This is not a bug in Better Content Archiving — the app is behaving correctly by detecting and reporting the problem. The root cause is a data inconsistency in your Confluence site: one or more published pages (with status CURRENT) have parent pages that are in DRAFT status. This is an invalid state that Confluence does not expect and that causes the REST API to fail when paging through the content of the affected space.

Next steps:

  1. Open a support ticket with Midori so we can confirm the likely root cause.
  2. We will then ask you to open a support ticket with Atlassian and share it with us.
  3. Once Atlassian resolves the data inconsistency, the paging errors should disappear and the job should process those spaces successfully.

As a workaround, you may also exclude the problematic spaces. This is not recommended as a long-term solution, but it can help you to get the app working while waiting for Atlassian to fix the underlying issue.

Content events (such as page views or page updates) are noticeably delayed.

In some Confluence Cloud environments, content events are delivered to apps with a significant delay. This means that actions triggered by page views, page updates, or similar events may appear to happen later than expected — for example, the last-viewed date of a page might not be updated promptly after someone visits it.

This is a platform-level limitation in Confluence Cloud and is tracked in Atlassian's public issue tracker: ECO-1403. Only Atlassian can improve the delivery speed of content events for all apps on the platform.

If you are affected by this issue, please vote for and comment on ECO-1403 to help Atlassian prioritise a fix.

Contents are not archived, but silently left in place.

As an additional symptom, you can also see less-than-expected count in the "Contents archived" audit log metric.

This can occur if any of these are valid:

  • Your Confluence site is on the Free license plan, which does not support archiving. You need at least the Standard plan to support it. (This is a limitation imposed by Confluence, not a limitation of the Better Content Archiving app.)
  • You are trying to archive a blog post. Archiving blog posts is not supported by Confluence. (You can still use the "delete" automation action on blog posts.)
  • The app cannot archive the page because of insufficient permissions. To fix it, fix the access control settings, then re-run the "Archive contents" job.

To fix it, verify and fix all the potential reasons above, then try again.

Content status overview

On the "Content status overview" gadget, the "Contents" count is not equal to the sum of the status cell counts.

It is normal. The difference is caused by content restrictions used in the space.

Example: if you have 100 pages in a space, but one is restricted from the app user, then the app will not be able to refresh its status. In this case, the "Content" value will be 100 (the precise number of contents), but the sum of the status cell values will be 99. Also, the "Tracked" value will be 99%, the ratio between the two.

For a space to be tracked 100%, fix the content restrictions so that the app can access every content in the space.

On the "Content status overview" gadget, "Refresh needed" is shown at a space, but a refresh doesn't help.

This occurs when the app cannot refresh the status of the pages (and blog posts) in the space because of insufficient permissions.

To fix it, fix the access control settings, then re-run the "Refresh content status" job.

Setup and environment

The app is failing due to network restrictions that block access to required external URLs.

If your organization uses a firewall and requires URL whitelisting, please ensure the following addresses are allowed to ensure Better Content Archiving functions correctly:

Space icons are not visible in Firefox, a placeholder is displayed instead.

This is a known bug (ECO-303) that can only be fixed by Atlassian.

As a workaround, you can disable "Enhanced Tracking Protection" for your Confluence site in Firefox.

Questions?

Ask us any time.