In this page
Instead of the content status, I see the "Status not available!" error message.
On the "Content status overview" gadget, the "Contents" count is not equal to the sum of the status cell counts.
On the "Content status overview" gadget, "Refresh needed" is shown at a space, but a refresh doesn't help.
Contents are not archived, but silently left in place.
The app is failing due to network restrictions that block access to required external URLs.
Frequent problems and solutions
Instead of the content status, I see the "Status not available!" error message.
This occurs when the app cannot set the status of the page (or blog post) because of insufficient permissions.
To fix it, fix the access control settings, then re-open the content status indicator.
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.
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.
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:
- IP addresses and domains for Atlassian cloud apps — this is the same requirement for all Atlassian apps.
- midori-carchc-prod-prod.s3.eu-west-1.amazonaws.com — for the app's static logo image.
Questions?
Ask us any time.