Delete Job | Dadosfera Maestro Platform API

Overview

Permanently deletes a job object from within a pipeline. A job represents an individual data processing step inside a pipeline (e.g., a source connector, transformation, or destination loader). This operation cannot be undone.

Path Parameters

Example

Delete a Job

DELETE /platform/jobs/job_7a2f3b4c_8d9e_0f1a_2b3c_4d5e6f7a8b9c

Response (200 OK):

{
  "job_id": "job_7a2f3b4c_8d9e_0f1a_2b3c_4d5e6f7a8b9c",
  "status": "JOB_DELETED"
}

What Gets Deleted

When you delete a job, the following resources are permanently removed:

Error Responses

404 Not Found

{
  "detail": "job_id job_7a2f3b4c_8d9e_0f1a_2b3c_4d5e6f7a8b9c not found!!"
}

500 Internal Server Error

{
  "detail": "Unable to complete transaction due to database error"
}

Important Considerations

Before Deleting

• Verify the job ID — Deletion is permanent and cannot be undone
• Check pipeline state — Consider pausing the parent pipeline before deleting one of its jobs to avoid partial execution
• Export configuration — If needed, retrieve the job configuration using GET /platform/pipeline/:pipelineId before deleting

What is NOT Deleted

• Destination tables — Data already loaded to the destination remains intact
• Source data — Original data in source systems is not affected
• Pipeline — The parent pipeline is preserved; only the individual job is removed

Use Cases

Remove an Unused Connector from a Pipeline

# 1. Get the pipeline details to find the job ID
GET /platform/pipeline/1b33ad2f_33d3_4837_9eeb_83c82c8b909d

# 2. Pause the pipeline (recommended)
POST /platform/pipeline/pause

# 3. Delete the job
DELETE /platform/jobs/job_7a2f3b4c_8d9e_0f1a_2b3c_4d5e6f7a8b9c

Notes

• Deleting a job is a destructive operation — ensure the correct jobId is used
• To delete the entire pipeline (including all jobs), use DELETE /platform/pipeline/:pipelineId
• To update a job's input configuration instead, use PUT /platform/jobs/:jobId/input