Skip to main content

How the daily run works

In briefThe daily run is what happens after a workflow is built: its jobs move through statuses as dependencies are satisfied, run on agents, and report back. Every job status belongs to a family — held, waiting, running, pending-term, terminal, under review or lost in failover — and a finished job passes briefly through pending-term before its dependents are released.

WhereOperations › Processes, where operators watch and act on the run. The statuses reference lists every status.

When

  • You are reading a job's status and want to know whether it is working as designed.
  • A job seems stuck and you need to tell a wait from a fault.
  • A workflow will not complete although its jobs look finished.

How

  1. Identify the job's status family.
  2. For a waiting job, find what it waits on — a dependency, its start time, a resource or an agent.
  3. For a failed job, respond from the Operator response guide: mark it fixed, restart, skip, cancel, mark it finished OK or failed, or close the workflow.
Notes
  • Pending-term is transitional: completion is being made durable before dependents are released. Cancelled, initialization-error and missed-start-time jobs skip it and settle at once.
  • The run survives a restart; every status change is saved as it happens.
  • On hold is intentional until released.
Watch out
  • Under review is not terminal. The workflow stays in process until you resolve the job or close the workflow.
  • Lost in Failover is not terminal either. Check the job on its machine, then mark it finished OK or failed; until then its dependents wait.
  • A job that stays in pending-term for a long time is worth investigating; a momentary one is not.