In this page

Frequent problems and solutions

Instead of the content status, I see the "Status not available!" error message.

When viewing a page or a blog post, the message "Status not available!" is shown instead of the actual content status.

This occurs when the app cannot access the given page or blog post.

Why? The app is represented by an artificial user called "Better Content Archiving" on your Confluence site. To the app user the same permissions are applied as to any human user. Therefore, the app will not be able to access a content:

  1. If the app user doesn't have the required space permissions on the space that contains the content.
  2. If the content restrictions applied to the content disallow the app user access the that.

To fix both cases, just open the content status indicator and follow the instructions.

Instead of the content status, I see the "Error!" generic error message for all pages and blog posts.

This occurs if you activated the IP allowlist feature on your Confluence Cloud site.

It causes the following symptoms by blocking certain mechanisms of the app:

  • Content status indicator:
    • Before opening the content status indicator, the status reads "Error!". Hovering over it displays the "Failed to get content status!" message.
    • Upon opening the content status indicator, the status changes to "Status not available yet!", then to a valid status. The box contains no other information and the buttons inside it are disabled.
  • App space permissions:
    • Accessing the screen displays a "Failed to read app user!" error.

To fix this, you need to extend your IP allowlist:

  1. Go to the Published IP address ranges for outgoing connections for Forge apps changelog page.
  2. Click "More details" and copy the IP address ranges from the list. (Adding these entries to your IP allowlist is perfectly secure, as these are published by Atlassian in their official Forge documentation.)
  3. Add the list to your Confluence Cloud site's IP allowlist.

Some pages are ignored by archiving and silently kept in place.

As a symptom, you also see less contents in the Audit Log metrics (i.e. "Contents archived") than expected.

There may be multiple reasons behind this:

  • The Better Content Archiving app has a dedicated user account to access Confluence data. If this app user has no "archive" permission on a space, archiving actions will be skipped.
  • If your Confluence is on a Free license plan, archiving is not supported at all. You need a Standard or Premium plan which supports the archiving feature. (This is a limitation imposed by Confluence, not a limitation of the Better Content Archiving app.)
  • If your content (or one of its parent contents) is view restricted and you forget to add access for the Better Content Archiving app user, then the app simply won't see the content to be archived, therefore it will skip pages like that.
  • You are trying to archive a blog post. Archiving blog posts is not supported by Confluence, but you can still use the "delete" automation action in this case.

Questions?

Ask us any time.