Automatic Runs
Automatic runs are report executions that happen on a schedule without user involvement. Every such run is logged in the history with type Automatic.
How automatic runs work
- The workspace has an internal scheduler that tracks all active schedules
- When the run time arrives, the scheduler creates an execution task
- The task is queued with status Pending
- Once resources are free, the task begins executing (status Running)
- On completion — Completed, Partial, or Failed
Before you begin
- The schedule must be enabled in the report's settings
- The connection must be active at the time of the run
- The output sheet must exist and be writable
Automatic run specifics
Queueing
If several reports are scheduled for the same time, they run sequentially in priority order: reports with an earlier last-run time go first, and ties are broken alphabetically by name.
Parallelism
Within a single workspace, a limited number of reports can run simultaneously (depends on the plan). The rest wait in the queue.
Skipped runs
A run may be skipped if: the connection is inactive, the previous run of the same report is still executing, the output sheet is unavailable (deleted, no permissions), the parallel-run limit has been reached, or the wait timed out. A skipped run is marked in the history with status Missed.
Retries
On a connection error, the system makes up to 3 retries with exponential backoff (1 min, 5 min, 15 min).
How to verify
- In the run history, automatic runs are marked with type Automatic
- Hovering over the status shows additional information (time in queue, number of attempts)
- The Schedule section shows the last and next run times
Related articles
- Manual Run — running manually
- Scheduling — configuring frequency
- Statuses — description of all statuses
- Missed Runs — details on Missed
- Progress — tracking execution