Job executions

A job execution is a concrete run of a job definition. It records when the job started, which tasks were executed, the inputs and outputs used, and the final status of the run.

Job execution status

During its lifecycle, a job execution can move through several statuses:

• PENDING: The execution has been created but has not started yet. This can happen when the job is queued by a pipeline or scheduled for a later time.
• RUNNING: The execution is in progress and tasks are actively being processed.
• COMPLETED: The execution finished successfully; all required tasks completed without errors.
• USER_ERROR: The execution ended with errors related to user‑controlled data or configuration. Examples include:
  • Invalid or missing user inputs.
  • Business or quota violations (for example, exceeding a limit when creating items in a table).
• FAILED: The execution ended with errors caused by technical issues. This can result from an invalid job definition, infrastructure problems, or unexpected platform errors. In such cases, contact our support team for assistance.
• TERMINATED: The execution was explicitly stopped by a user before completion.
• TIMEDOUT: The execution was automatically stopped because it exceeded the configured maximum runtime (timeoutSeconds in the job definition).

flowchart LR
    PENDING["PENDING"]
    PENDING:::diagramLightGrayElement
    RUNNING["RUNNING"]
    RUNNING:::diagramBlueElement
    COMPLETED["COMPLETED"]
    COMPLETED:::diagramGreenElement
    USER_ERROR["USER_ERROR"]
    USER_ERROR:::diagramRedElement
    FAILED["FAILED"]
    FAILED:::diagramDarkRedElement
    TERMINATED["TERMINATED"]
    TERMINATED:::diagramGrayElement
    TIMEDOUT["TIMEDOUT"]
    TIMEDOUT:::diagramRedElement
    PENDING --> RUNNING
    RUNNING --> COMPLETED
    RUNNING --> USER_ERROR
    RUNNING --> TIMEDOUT
    RUNNING --> FAILED
    RUNNING --> TERMINATED
    PENDING --> TERMINATED

The diagram above illustrates the possible transitions between the various job execution statuses.