Skip to main content

Pause pipeline

POST 
/platform/pipeline/pause

Suspend future scheduled executions for pipeline_id while preserving configuration and history. The source explains that currently running executions continue; use run cancellation if a running execution must stop.

Contract caveat​

Source examples send only pipeline_id and say Maestro injects customer_id. The imported DagParams requires both fields. This public-versus-downstream discrepancy remains unresolved for the deployed API. Source already-paused and not-found error examples are not enumerated in this operation's response map and are not additional schema guarantees.

Use Unpause pipeline to resume scheduling. Pausing does not delete jobs or historical runs.

Request​

Responses​

Pipeline paused