Support

The app is in read-only mode, which happens when it is not licensed — for example after a trial ends or before a subscription is activated. Listing, search and dry run keep working; write jobs are refused both in the UI and on the server. Once the license is active in Apps → Manage apps, the buttons come back. (On a Forge development site there is no license at all, so the app is read-only there by design.)

Jobs run in the background on Atlassian in resumable chunks, so closing the tab is fine — reopen the app and check the Jobs tab. Each page is processed as "add the new label, then remove the old one", so a job that stops partway leaves pages either untouched or fully converted, never with labels lost. If a job shows failed (including enqueue_failed or abandoned after 7 days without progress), press Resume: it continues from where it stopped and skips what is already done. Rate limits (HTTP 429) are retried automatically.

Version 1 covers pages and blog posts (global labels). Attachment labels and space labels are not yet handled. The job runs with the permissions of the person who started it, so pages you cannot edit are not listed in the dry run and are not changed — ask a user with the right permissions to run the job, or run it again after permissions are fixed. Label names must be lower-case with no spaces or the characters : ; , . ? & [ ] ( ) # ^ * @ ! ' ".

No, it is not permanent. The app calls Confluence's normal delete, which moves the attachment to the space trash; it never purges. A space administrator can restore it — see Restoring attachments above. Before anything is deleted you get a dry run with the count, total size and largest files, and every job writes a log (trashed, already-gone, skipped:version-changed, skipped:moved, failed) you can review in the Jobs tab. If an attachment was re-uploaded or moved to another page after the scan, the app skips it rather than deleting a version it did not check.

Attachment Sweep is shown only to site administrators. If you are not a site admin, the entry does not appear. Also, everything the app does runs with your own permissions: attachments and pages in spaces you cannot view are never scanned or listed. Scanning and the deletion dry run work without a license; creating a delete job requires an active license.

The scan looks for references in page and blog-post bodies (both the classic storage format and the new editor's ADF), in attachment-list and gallery macros, and in page properties such as cover images. Attachments referenced from another page show as referenced by other page, cover images as cover picture, and neither is offered for deletion. Things that can still cause surprises: a space-limited scan does not detect references from other spaces — run a site-wide scan if in doubt; attachments newer than the minimum age (7 days by default) are never listed; and a scan result older than 24 hours must be re-run before you can delete from it. Enable "also read drafts" if references exist only in unpublished drafts. If you still see a wrong result, email us the attachment's page URL and file name.

Open the page and choose Set review policy from the page's "…" menu, or click the Review: not set item in the byline under the title. Pick a reviewer, then either a due date or a review interval in days (the interval sets the next date each time the page is marked reviewed), and save. The policy is stored as a content property on the page; the page body and page version are not touched. To mark a page reviewed, use Mark as reviewed in the byline dialog or in the banner shown on due and overdue pages — the due date moves to today plus the interval. Site administrators can assign, mark reviewed or clear policies on many pages at once from the app's dashboard (Apps menu → Page Review Reminders → Overview): select rows, choose the action, check the dry-run count and confirm. Setting or changing a policy requires an active license; viewing works without one.

The app does not send email itself. Once a day it scans the pages that have a policy; for each page that is due soon or overdue it posts a footer comment on that page that @mentions the reviewer (or the page owner, if no reviewer is set). Confluence then delivers its own notification for the mention — in the notification drawer (bell icon) and by email, according to your Confluence notification settings. So check the page's comments and the bell first. A page gets at most one reminder per 30 days, and the same due date is not mentioned twice unless the state changes (for example from due soon to overdue); after you mark the page reviewed, the next due date starts a new cycle. Confluence itself may not email mention notifications on a site still in its trial period, or for repeated mentions on the same page. Reminders are only posted when the license is active and notifications are enabled in Settings. Independently of comments, due and overdue pages show a banner at the top of the page, the byline reads Review due soon or Overdue, and your own due pages are listed under Pages to review on the Confluence Home feed.

The app keeps its own index of pages that carry a review policy, because Confluence's search cannot filter pages by that property. Every policy set through the app is added to the index automatically. Policies that were written directly through the REST API, or created before an app upgrade, are not — for those, a site administrator opens the dashboard's Settings tab and presses Rebuild index. This starts a reindex job (visible on the Jobs tab) that enumerates every page on the site and reads its review property, so it costs roughly one API point per page. On a large site it may hit the daily point budget (scanBudgetPoints in Settings, 5,000 by default) and stop with a "carried over" note; it then continues the next day automatically, or right away with Continue rebuilding. The daily scan waits until the rebuild has finished. Afterwards, press Scan now to refresh the Overview. Rebuilding does not require a license — it only writes the app's own storage. The Overview's Check index shows how many pages are indexed and when the index was last rebuilt.