Job History - Pipelines

The Job History – Pipelines page displays current and historical information about pipeline jobs.

The Job History – Pipelines page shows pipeline-level job information, including:

  • Name of the pipeline's parent wrapper
  • The current status of all pipelines, including pipelines that are currently running, ran successfully, not running, already running, failed and so on. For more information about pipeline statuses, see Data Hub Pipeline Statuses.
  • Run type, including incremental and historical

  • The job start and end times. Pipelines that are running show no end time until the job finishes.
  • The duration time of the pipeline job.

  • For API pipelines, details include the number of entities changed when the pipeline ran, the number of API calls made, the number of partitions, and the API response GB size.

Note: The wrapper name in bold reflects a summary status for both the wrapper and its pipelines. This summary wrapper has a dash (-) in the Pipeline column.

See Alert Management for details about failed wrappers and pipelines.

Data Hub pipeline statuses

Pipeline statuses show their current state, including whether a pipeline was run successfully or encountered issues.

Pipeline Statuses and Descriptions

StatusDescription
SuccessCompleted successfully
RunningActively running
FailedFailed to complete. When a pipeline fails, the wrapper stops running with a Failed status.
Already RunningAnother instance of the pipeline is already running. The wrapper will run the next pipeline in the sequence
Skipped The tenant is configured to prevent a pipeline from running
API DisabledThe pipeline was skipped because of a technical issue on the tenant
DataHub GCP Permissions IssueFor Enterprise customers who own and manage their Data Hub GCP projects, the pipeline failed to update data in BigQuery because the Data Hub service account does not have access to the GCP project
KillPipelines currently running in a wrapper that was manually stopped have this status while the process stops them. After they are stopped, pipelines have a status of Success or Terminated
TerminatedThe wrapper job was manually stopped while the pipeline was running, so the pipeline stopped before it finished running

Filter Job History pages

By default, the Job History pages display 50 items (rows). You can filter the pages to show more or fewer items.

  1. Click the Items Per Page drop-down list and select a value. You can filter the page to view the following number of items at a time: 10, 20, 30, 50, 100, 250, 500.
  2. To navigate through the pages, click Next and Prev.