In this page

What does the Execute Automations job do?

This job executes automations on the specified contents in your Confluence.

Even though the automations have a configured schedule, you can run this job manually, but it will not affect the next scheduled run. For example, if an automation is scheduled for every Monday, it will be executed right now, but also on the next Monday.

How it works

Conceptually:

  1. The job processes all spaces except the excluded ones (site scope) or only one specific space (space scope).
    1. It takes the automation scheme applied to the space.
    2. Executes all automations in the scheme from top to bottom:
      1. Queries the contents matching the specified CQL query
      2. Executes the specified action on the content list.

Note: Contents will only be processed by the first automation which has a matching CQL query. If the action cannot be performed (e.g. the action is "archive" but your Confluence license does not support archiving) then the action will be skipped and the unprocessed contents will NOT be passed to the next action of the scheme.

Scheduled runs

This job runs whenever an automation action is due, according to its configured schedule.

Manual runs

Beware: Running this job manually will execute all automations in the scheme, regardless of schedule! Running this job can be time-consuming for large spaces. Prefer a space scope execution over a site scope one, since it's faster and less likely to fail due to transient issues like network errors or rate limiting.

You should only run this job manually in one of the following situations:

  • If you really want to execute all automations immediately (and ignore their actual schedule).
  • If the Midori support team asks for that.

Supported metrics

This job saves the following metrics to the job audit log:

  1. Spaces processed
  2. Spaces total
  3. Contents archived
  4. Contents deleted
  5. Contents purged

Questions?

Ask us any time.