workflow_disabled
workflow_disabled
Section titled “workflow_disabled”HTTP status: 409 Conflict
How to fix
Section titled “How to fix”- Open the workflow in the dashboard. Under Workflows → <your workflow>, the header carries an Enabled/Disabled toggle. Flip it.
- Or via API:
PATCH /api/v1/workflows/{id}with body{ "enabled": true }. - Confirm the state took by fetching
GET /api/v1/workflows/{id}and checkingenabled: truein the response. - Retry the submission that failed with this code — once the workflow is re-enabled, the same payload succeeds.
What this means
Section titled “What this means”The workflow exists and is valid, but its owner explicitly disabled it. We block job submissions against disabled workflows so that pausing a workflow during an incident actually stops new work from queuing up. This is distinct from not_found (workflow deleted) and invalid_workflow (workflow shape broken).
Related errors
Section titled “Related errors”not_found— workflow deleted entirelyinvalid_workflow— workflow shape fails DAG validationjob_terminal— job already finished, can't mutate
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm the workflow's enabled state in our logs.