workflow_inactive — Workflow inactive

What causes it

• A live-mode trigger on a draft cascade ("Draft workflows run in test mode only. Activate the workflow before triggering it live."). Test-mode triggers on drafts are allowed.
• A batch create, resume, or retry on a cascade that is not active. Batches need an active cascade in test mode too, so a sandbox account (not approved for production) gets this on every batch create.
• A re-evaluation of an execution whose cascade has since been deactivated.

How to fix it

1. Activate the cascade (`PATCH /workflows/{id}` with `active: true`, or the Activate toggle in the builder) and resend.
2. For a one-off test run against a draft, trigger it with `execution_mode: "test"`.
3. A sandbox account cannot activate a cascade, so it cannot run batches. Get approved for production through the activation form at /activate first.

Operations that return it

• POST /workflows/{id}/trigger Trigger a workflow
• POST /workflows/{id}/batches Create a batch from N rows
• POST /batches/{id}/resume Resume an interrupted batch
• POST /batches/{id}/retry_failed Retry failed and skipped rows
• POST /executions/{id}/re_evaluations Re-evaluate an execution

Example response

HTTP/1.1 409 Conflict · Content-Type: application/json

{
  "error": {
    "code": "workflow_inactive",
    "message": "Only active workflows can run batches through the public API.",
    "details": [],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/workflow_inactive"
  }
}

Related

• Concepts › Cascades