Scheduled Jobs

The administration console allows you to schedule various administrative jobs in Confluence, so that they are executed at regular time intervals. The types of jobs which can be scheduled cover:

  • Confluence site backups
  • Storage optimization jobs to clear Confluence's temporary files and caches
  • Index optimization jobs to ensure Confluence's search index is up to date
  • Mail queue optimization jobs to ensure Confluence's mail queue is maintained and notifications have been sent.

(info) You'll need System Administrator permissions in order to edit and manually run jobs.

On this page:

Related pages:

Accessing Confluence's scheduled jobs configuration

To access Confluence's Scheduled Jobs configuration page:

  1. Go to  > General Configuration > Scheduled Jobs
  2. All scheduled jobs are listed with:
    • Status - the job's status, which is either 'Scheduled' (it it is currently enabled) or 'Disabled'.
    • Last Execution - the date and time when the job was last executed. This field will be empty of the job was never executed.
    • Next Execution -the date and time when the job is next scheduled to be executed. This field will contain dash symbol ('-') if the job is disabled.
    • Avg. Duration - the length of time (in milliseconds) that it took to complete the job (the last time it ran).
    • Actions - Options to edit the job's schedule, run it manually, view the history or disable the job.

Screenshot: Scheduled Jobs

Running a job manually

To run a job manually head to the Scheduled Jobs list and choose Run next to the job. It will run immediately. 

Not all jobs can be run manually. 

Changing a job's schedule

To change a job's schedule:

  1. Choose Edit next to the job you want to change. 
  2. Enter the new day or time to run the job as a cron expression - there's more info about cron expressions below
  3. Save your changes to the job's schedule, or Revert back to the default setting.

Not all jobs' schedules are configurable.

Screenshot: Configuring a Job Schedule

Disabling or re-enabling a job

By default, all jobs in Confluence are enabled.

Use the Disable / Enable links in the action column to disable and re-enable each job.

Not all jobs in Confluence can be disabled.

Viewing a job's execution history

To see when a job was last run, and how long the job took to run, click the History link beside the job. 

If a job has not run at least once the History link won't appear.

Screenshot: Job Execution History

(warning) Execution history is not available in Confluence Data Center. 

Types of jobs

Here's a summary of some of the scheduled jobs that you may want to adjust.

Job Name


Execution Behavior

Default Schedule

Back Up Confluence

Performs a backup of your entire Confluence site.

Per cluster

At 2am every day

Check Cluster Safety

For clustered Confluence installations, this job ensures that only one Confluence instance in the cluster writes to the database at a time.
For standard (non-clustered) editions of Confluence, this job is useful for alerting customers who have accidentally connected a second Confluence instance to a Confluence database which is already in use.

Per cluster

Every 30 seconds

Clean Journal Entries

Periodically clears journal entries that have already been processed to ensure that its size does not grow indefinitely.

Per clusterAt 2am every day

Clean Temporary Directory

Cleans up temporary files generated in the <confluence-home>/temp directory. This temp directory is created by exports etc.
(info) This doesn't include the temp directory located in the confluence install directory. 

Per node

At 4am every day

Clear Expired Mail Errors

Clears notification errors in the mail error queue. A notification error is sent to the mail error queue whenever the notification fails to be sent due to an error.

Per cluster

At 3am every day

Clear Expired Remember Me Tokens

Clears all expired 'Remember Me' tokens from the Confluence site. Remember Me tokens expire after two weeks.

Per cluster

On the 20th of each month

Email Daily Reports

Emails a daily summary report of all Confluence changes to all subscribers.
(info) Since each email report only records changes from the last 24-hour period, it is recommended that you only change the time of this job while keeping the job's frequency to 24 hours.

Per cluster

At 12am every day

Flush Change Index Queue

Flushes the Change Index Queue so Confluence's search results stay up to date.

Per nodeEvery minute
Flush Content Index QueueFlushes the Content Index Queue so Confluence's search results stay up to date.Per nodeEvery minute
Flush Edge Index QueueFlushes the Edge Index Queue so Confluence's search results stay up to date.Per nodeEvery 30 seconds

Flush Local Task Queue

Flushes the local task queue. (These are internal Confluence tasks that are typically flushed at a high frequency.)

Per node

Every minute

Flush Mail Queue

Sends notifications that have been queued up in the mail queue. This doesn't include batched notifications. Edit the Send batched notifications job if you also want to change how often notifications are sent for changes to a page or blog post.

Per node

Every minute

Send batched notificationsSends email notifications containing all changes to a page or blog post since the last time the job ran. Increase the time for fewer emails or reduce the time if more immediate notifications are important in your site.  Per clusterEvery 10 minutes

Flush Task Queue

Flushes the task queue. (These are internal Confluence tasks that are typically flushed at a high frequency.)

Per node

Every minute

Send Recommended Updates EmailTriggers sending recommended update emails to users. The job runs hourly, but users will receive the notification weekly or daily, depending on the setting in their profile, at a time that matches their timezone.Per clusterHourly
Purge Old Job Run Details

Confluence stores the details of each scheduled job that is run in the scheduler_run_details table in your database. In order to keep this table small for troubleshooting and debugging, the Purge Old Job Run Details job regularly removes the details of:

  • successful jobs run more than 90 days ago
  • unsuccessful jobs run more than 7 days ago

You can override these settings using the following system properties; jobs.limit.per.purge, and

Per clusterat 11pm every day

Property Entry Gardening

When a page is created from a blueprint, some data is left behind in the os_property table after the page is published. This job cleans up leftover data, which could contain personally identifiable information.

Per clusterAt 12am every day
Clean up unpublished Blueprint Page EntitiesThis job cleans up metadata stored about draft pages created from blueprints, which could contain personally identifiable information.Per clusterAt 2:23am every day
Synchrony data eviction (soft)Evicts Synchrony data for any content that has not been modified in the last 3 days, and does not have an active editor session.  See How to remove Synchrony data for more information.Per clusterEvery 10 minutes

Synchrony data eviction (hard)

Evicts Synchrony data for any content that is 15 days or older, regardless of whether it has been modified more recently. See How to remove Synchrony data for more information.

Per clusterDisabled by default

Cron expressions

A cron expression is a string of 6-7 'time interval' fields that defines the frequency with which a job is executed. Each of these fields can be expressed as either a numerical value or a special character and each field is separated by at least one space or tab character.

The table below is shows the order of time interval fields in a cron expression and each field's permitted numerical values.

You can specify a special character instead of a numerical value for any field in the cron expression to provide flexibility in defining a job's frequency. Common special characters include:

  • '*' — a 'wild card' that indicates 'all permitted values'.
  • '?' — indicates 'ignore this time interval' in the cron expression. That is, the cron expression will not be bound by the time interval (such as 'Month', 'Day of week' or 'Year') to which this character is specified.

For more information about cron expressions, please refer to the Cron Trigger tutorial on the Quartz website.

Order in cron

Time interval
















Day of month





1-12 or JAN-DEC



Day of week

1-7 or SUN-SAT






* Excluding special characters.

Last modified on Dec 14, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.