Product
Runs & monitoring
Run history, status values, and how orchestrators report success and failure.
What is a run?
A run is an audit record for one pipeline execution: start time, end time, status, and optional metadata.
Runs link to check results so you can drill from a failed pipeline to specific quality violations.
Airflow task SUCCESS alone does not create a run — your DAG must POST to DataXPipe.
Status values
- running — execution in progress
- success / completed — finished OK
- failed — pipeline or checks failed
- Include started_at and ended_at (ISO-8601) for duration in the Runs table
In the app
The Runs page lists execution history across your organization.
The Dashboard shows recent runs and success rate.
Via the API
# Start a run (from your orchestrator)
curl -X POST https://api.dataxpipe.com/api/v1/runs/ \
-H "X-API-KEY: dxp_your_key" \
-H "Content-Type: application/json" \
-d '{"pipeline_id":"orders_sync","status":"running"}'
# List runs for a pipeline
curl "https://api.dataxpipe.com/api/v1/runs/pipeline/orders_sync?limit=50" \
-H "X-API-KEY: dxp_your_key"Linking checks to runs
Include run_id when posting check results so failures correlate with a specific execution.
Alerting
Poll the runs API for failed status, or forward orchestrator failure webhooks and enrich alerts with lineage from DataXPipe.
Slack and email alerting from failed checks is on the roadmap — contact us for early access.