Overview

Resume a paused pipeline to allow scheduled and manual executions again.

Request Body

Field	Type	Required	Description
`pipeline_id`	string	Yes	The UUID of the pipeline to unpause

Note: The customer_id is automatically injected by Maestro from the authenticated user's JWT token.

Examples

Unpause a Pipeline

POST /platform/pipeline/unpause

{
  "pipeline_id": "1b33ad2f-33d3-4837-9eeb-83c82c8b909d"
}

Response (200 OK):

{
  "status": true,
  "data": {
    "message": "Pipeline unpaused successfully",
    "pipeline_id": "1b33ad2f_33d3_4837_9eeb_83c82c8b909d"
  }
}

Python Example

import requests

BASE_URL = "https://maestro.dadosfera.ai"
PIPELINE_ID = "1b33ad2f-33d3-4837-9eeb-83c82c8b909d"

# Unpause pipeline
response = requests.post(
    f"{BASE_URL}/platform/pipeline/unpause",
    headers=headers,
    json={"pipeline_id": PIPELINE_ID}
)

print(response.json())

Error Responses

404 Not Found - Pipeline Not Found

{
  "detail": {
    "status": false,
    "exception_type": "PipelineNotFound",
    "traceback": "Pipeline with id 1b33ad2f_33d3_4837_9eeb_83c82c8b909d not found",
    "data": null
  }
}

400 Bad Request - Not Paused

{
  "detail": {
    "status": false,
    "exception_type": "PipelineNotPaused",
    "traceback": "Pipeline is not paused",
    "data": null
  }
}

Pipeline ID Format

The pipeline_id can be provided in either format:

Hyphenated UUID: 1b33ad2f-33d3-4837-9eeb-83c82c8b909d
Underscored: 1b33ad2f_33d3_4837_9eeb_83c82c8b909d

Maestro automatically normalizes the ID before forwarding to Platform-API.

Behavior

When a pipeline is unpaused:

Scheduled cron executions resume according to the pipeline's cron schedule
Manual executions via POST /platform/pipeline/execute are allowed
The pipeline status changes back to active
The next scheduled run will occur at the next cron trigger time

Notes

Use POST /platform/pipeline/pause to pause the pipeline again
If you need an immediate execution after unpausing, call POST /platform/pipeline/execute