# `PATCH /v1/workflows/{id}`: Change a workflow

Changes the fields sent; the others stay. A draft stays a draft. A published workflow stays published and the change applies to new verifications at once, as a save in the dashboard does (live: true in the response); verifications already started keep the definition they started with. The same checks as at publish apply to a published workflow's documents, and turning on the FINMA profile needs the plan that includes it. active: false takes a workflow out of use (sessions with it are refused) and can be undone; reactivating a production workflow takes a slot of the plan. The environment cannot change: copy the workflow in the dashboard instead. There is no DELETE. Needs the workflows:write scope.

Parameters:
- `id` (path, string, required)

Body:
- `name` (string)
- `description` (string)
- `minimum_age` (integer, nullable)
- `ip_countries` (object, nullable)
- `location_countries` (object, nullable)
- `video_hours` (object, nullable)
- `four_eyes` (boolean)
- `outcome_overrides` (object)
- `score_thresholds` (object)
- `status_rules` (array of object)
- `steps` (array of string)
- `step_configs` (object)
- `document_rules` (array of object)
- `active` (boolean): false takes the workflow out of use; it can be turned on again.

Responses:
- 200: The workflow after the change; live says whether new verifications run it.
- 400: Invalid definition or unknown field; errors lists the problems.
- 401: Missing, unknown or expired API key.
- 402: Reactivating would exceed the plan's active production workflows, or the FINMA profile is not in the plan (code plan_required).
- 403: The key lacks workflows:write, the body names another environment, or the key was issued through Connect with secuveri without the workflows:write setup right.
- 404: No workflow with this id in the key's organization and environment.
- 429: More than 30 workflow changes in a minute.
