The scheduler manages long-running scheduled tasks. A scheduled task periodically triggers an action on a job or report
at the specified frequency. For example, a scheduled task can start or stop a job or generate a data delivery report
on a weekly or monthly basis.

As a scheduled task runs, you can monitor the status of the task and view the number of times the task has triggered
an action on a job or report. You can also view an audit of all changes made to the scheduled task.

Missed Execution Handling

When a scheduled task is paused, it might miss scheduled executions. You can
configure how each task handles missed executions.

For example, let's say that a scheduled task
generates a report daily at 10 pm that includes job metrics for the last 24 hours.
However, you paused the scheduled task for three days such that the task missed
triggering the report three times. When the scheduled task returns to a running state,
the task can ignore all missed executions, run all three missed executions, or run one
missed execution.

Configure one of the following ways to handle missed executions:

Ignore

When the scheduled task is resumed, it ignores any missed executions and
then continues triggering the job or report based on the defined
schedule.

Run All

When the scheduled task is resumed, it immediately runs all missed
executions and then continues triggering the job or report based on the
defined schedule. Use the Run All option for reports only.

When you configure the Run All option for scheduled jobs, the scheduler
triggers multiple job starts or stops at the same time - which results in
the job being run or stopped once. For example, if a paused scheduled task
missed two executions for a job start, and then it immediately triggers both
executions when resumed, the job is still only run once. The second
execution is triggered, but fails to run because the job is already
active.

When you configure the Run All option for scheduled reports, the scheduler
runs the missed executions based on the scheduled time that the report
should have been triggered. For example, let's say that you scheduled a
report to run every Saturday at 9 am that includes job metrics for the last
7 days. You pause the scheduled task for two weeks such that the task missed
triggering the report two times. When the task is resumed, it immediately
runs the missed reports according to the missed scheduled times. The
scheduler triggers the following two reports that contain different data:

Report with a scheduled time of Saturday April 21 at 9 am includes
job metrics from Saturday April 14 through Friday April 20.

Report with a scheduled time of Saturday April 28 at 9 am includes
job metrics from Saturday April 21 through Friday April 27.

Run Once

When the scheduled task is resumed, it immediately runs one missed execution
and then continues triggering the job or report based on the defined
schedule.

For a scheduled report, the scheduler runs only the last missed execution of
the report. If we use the same report example provided above, the scheduler
triggers only the following report:

Report with a scheduled time of Saturday April 28 at 9 am includes
job metrics from Saturday April 21 through Friday April 27.