Skip to main content

Resume pipeline

POST 
/platform/pipeline/unpause

Resume scheduled processing for a paused pipeline. The next execution follows its cron schedule; unpausing is not an immediate run request. Use Execute pipeline when an immediate execution is needed.

Contract caveat​

Source examples send only pipeline_id and say Maestro injects customer_id, but imported DagParams requires both. Verify deployed request behavior before omitting a schema-required field. Source 400 and 404 error examples are not enumerated in this response map.

Unpausing does not recreate jobs or discard history. Use Pause pipeline for another maintenance window.

Request​

Responses​

Pipeline unpaused