In this page

Refresh content owners job

What does it do?

This job refreshes the owner properties as needed in your Confluence.

Better Content Archiving for Confluence uses the concept of owners to track who is responsible for specific contents. For each individual content, you can set zero, one, or multiple Confluence users as owners or tree owners. The latter is inherited by all descendant contents in the page tree, automatically.

The app ensures that the inherited owner properties are always up-to-date on all contents, using the following strategy:

  1. When changes occur in a page tree that affect ownership inheritance (e.g., changing tree owners, moving, or deleting pages), event handlers update the properties incrementally to keep them accurate.
  2. In addition, the scheduler runs this job periodically to refresh the properties of owned content trees and correct any accidental discrepancies in the calculated fields.

How it works

Conceptually, the job runs either across all spaces (site scope) or on a single specific space (space scope).

The actions performed by the job slightly depend on how it has been started.

  1. It collects the contents for which ownership should be refreshed.
    • For scheduled executions, this only covers special cases – for example, contents where change propagation got stuck, or contents where incremental events could not keep everything up to date (such as when pages with tree owners are moved to the trash).
    • For manual executions, this covers a much broader set of contents: all owned items, meaning any content with either an owner or a tree owner assigned.
  2. It collects all children of the contents selected in the previous step, recursively. Then it recalculates and updates all owner related content properties as needed.
  3. If there were any contents marked as "dirty", the job clears the related flags.

Once the job has completed, the owner fields of all contents within scope will be fresh. After Confluence updates its internal indexes, CQL expressions should consistently return up-to-date owner information.

Scheduled runs

This job runs in site scope, once per day.

The job doesn’t start exactly at the top of the hour. Instead, it starts at a fixed, randomly assigned minute between the 10th and 35th minute of each hour – the exact minute is specific to your cloud instance. This helps distribute the overall load on the Confluence Cloud APIs more evenly.

Manual runs

Beware: Running this job can be very time-consuming for large spaces!

You should run this job manually only if:

  • If you tried to modify the owner of a content, but the app keeps displaying an error message that an update is still in progress while you think it should have finished already. In this case, try to run the job in space scope on the affected space only, to conserve resources.
  • If you included a previously excluded space, for which the job has not yet run recently. In this case, try to run the job in space scope on the affected space only, to conserve resources.
  • If the Midori support team asks for that.

Supported metrics

  1. Content owners refreshed

To understand what each metric means, please refer to the documentation on the job audit log.

Questions?

Ask us any time.