Skip to content

Pause and resume

Pausing a run stops new tasks from being scheduled while preserving accurate active-time accounting across the pause.

AgentDock Pro

Pausing and resuming a run is part of AIgency, available only in AgentDock Pro.

Pausing a run doesn't kill anything already in flight — it stops the scheduler from starting new tasks. Anything already running continues until it finishes naturally.

What pause actually does

A paused run records the moment it was paused as the start of a paused interval; resuming closes that interval. AIgency keeps a full list of these intervals rather than a single running total, so time spent paused can be excluded precisely from any task's active-time accounting — including across multiple pause/resume cycles in the same run, and across an app restart that happens mid-pause.

Note

Concurrency settings can only be changed while a run isn't actively running — pause the run first if you need to adjust global or per-agent concurrency limits. See Multi-agent orchestration.

Resuming

Resuming re-enables scheduling; tasks that were eligible to run before the pause (and any that became eligible during it) are picked up on the very next scheduling pass, the same as any other trigger.