Skip to main content
Extraction pipeline runs represent individual executions of an extraction pipeline. Each run reports a status along with timestamps and optional error messages.

Run statuses

Each run has a status: success, failure, or seen. Success indicates the pipeline completed without errors. Failure indicates an error occurred. Seen is used when the pipeline was observed but completion status is not yet known.

Monitoring data ingestion

You use runs to monitor the health and progress of your data ingestion processes. Filter runs by pipeline, status, or time range. Retrieve run details for troubleshooting failed executions or auditing successful ones.
Runs are created by extractors or custom code when they execute. You typically read runs rather than create them directly.

Key capabilities

  • List runs by pipeline, status, or time
  • Retrieve run details including errors
  • Monitor success and failure rates
  • Audit execution history for compliance
Last modified on April 23, 2026