Job Runs
A Job Run is a single execution instance of a Job Definition. Runs are created automatically by a CRON schedule or triggered manually. Once started, a Job Run is read-only — its configuration is inherited from the Job Definition at the time of execution.
Navigate to Workspace → Operations → Job Runs to view all runs and their current status.
Job Run Statuses
| Status | Description |
|---|---|
| Pending | The run has been created and is waiting to be picked up by Airflow |
| Queued | The run is queued in Airflow and waiting for an available worker pod |
| Running | The run is currently executing |
| Success | The run completed successfully |
| Completed | The run finished (alternative success state) |
| Failed | The run encountered an error and did not complete successfully |
| Cancelled | The run was manually stopped before completion |
| Skipped | The run was skipped (e.g., due to DAG catchup or concurrency configuration) |
| Unknown | The status could not be determined |
Metadata
Each Job Run exposes the following information:
| Field | Description |
|---|---|
| Job Definition | The definition this run was created from |
| Job Type | The operational category of the job |
| Status | The current execution status |
| Trigger Method | Whether the run was triggered by a schedule or manually |
| Execution Date | The scheduled execution date for this run |
| Start Date | When execution actually began |
| End Date | When execution completed or was terminated |
| Airflow DAG ID | The corresponding Airflow DAG identifier |
| Airflow Run ID | The unique Airflow run identifier for cross-referencing in Airflow |
| Logs | Detailed execution log, including error stacktraces for failed runs |
Filtering
Job Runs can be filtered by Job Type and Status to focus on specific workflows or investigate failures.
Cancellation
A Job Run that is currently in Pending, Queued, or Running state can be cancelled. Cancellation stops execution and marks the run as Cancelled. Logs up to the point of cancellation remain accessible.
Log Access
Logs are attached to each Job Run and provide a step-by-step record of execution. For failed runs, the log includes the full error stacktrace to assist with debugging. An external log URL may also be available for direct access to the Airflow task logs.