rollback-flow-version

Mark an earlier version of a process flow as the live one. The displaced version becomes rolled_back and numbering is left alone, so rolling back to v1 while v2 was live leaves v2 in the history and the NEXT promote is v3. This records which snapshot is live — it does NOT rewrite the flow's agents; read the snapshot from flow-versions (include_snapshot: true) and apply it yourself if you want the structure restored. Admin role required.

What it is called on each surface

The wire name is rollback-flow-version everywhere: it is what the Wexa MCP server advertises, the REST path is POST /v1/rollback-flow-version, and each SDK exposes it under its own language's naming convention.

Arguments

2 of the 2 arguments are required. Omitting a required one is refused before the tool runs, at the validation stage, so it costs nothing and changes nothing.

project_id, projectID, organization_id and executed_by are not arguments you pass: the platform binds all four from the credential you authenticated with, and both SDKs refuse them before the request leaves your process — see server-bound arguments.

What it returns

The three surfaces wrap this differently, and code written against one will not read another correctly — see return shape.

A real response, captured from a live call to rollback-flow-version:

snapshot came back populated and is shown as … here, because the real value runs to thousands of characters. Read it from your own call rather than from this page.

{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000182\",\"result\":{\"id\":\"fver_c9593de3-f85c-48bb-bf39-32c923cf467e\",\"agentflowId\":\"6ab1945e7566f41b5c28e308\",\"version\":1,\"status\":\"promoted\",\"snapshot\":\"\\u2026\",\"agentCount\":0,\"promotedBy\":\"6a79a770b6c128ccc24bfca7\",\"promotedAt\":\"2026-09-21T20:32:39.381Z\"}}"
    }
  ],
  "isError": false
}

{
  "lifecycle_id": "qlc_000182",
  "result": {
    "id": "fver_c9593de3-f85c-48bb-bf39-32c923cf467e",
    "agentflowId": "6ab1945e7566f41b5c28e308",
    "version": 1,
    "status": "promoted",
    "snapshot": "\u2026",
    "agentCount": 0,
    "promotedBy": "6a79a770b6c128ccc24bfca7",
    "promotedAt": "2026-09-21T20:32:39.381Z"
  }
}

// the object you get back IS the result — there is no `.result` to read
{
  id: 'fver_c9593de3-f85c-48bb-bf39-32c923cf467e',
  agentflowId: '6ab1945e7566f41b5c28e308',
  version: 1,
  status: 'promoted',
  snapshot: '…',
  agentCount: 0,
  promotedBy: '6a79a770b6c128ccc24bfca7',
  promotedAt: '2026-09-21T20:32:39.381Z'
}

// The TS SDK names these camelCase — lifecycleId, traceId — where Python uses
// lifecycle_id and trace_id. Both are non-enumerable: readable, but omitted by
// Object.keys() and JSON.stringify(). `result.lifecycleId` here is undefined.
result.lifecycleId // 'qlc_000182'

# a dict subclass; `result` is already unwrapped
{
 "id": "fver_c9593de3-f85c-48bb-bf39-32c923cf467e",
 "agentflowId": "6ab1945e7566f41b5c28e308",
 "version": 1,
 "status": "promoted",
 "snapshot": "\u2026",
 "agentCount": 0,
 "promotedBy": "6a79a770b6c128ccc24bfca7",
 "promotedAt": "2026-09-21T20:32:39.381Z"
}

out.lifecycle_id  # 'qlc_000182' — an attribute, not a key

Keeping the lifecycle_id is what lets you ask later why a call was allowed, refused or held.

Calling it

The same call on all four surfaces. Pick a tab once and every code block in the documentation follows it.

The ids in this example are real: they resolve against the project the documentation is written against, so the call runs as written once you point it at your own deployment. Swap them for the ids of your own objects.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "rollback-flow-version",
    "arguments": {
      "process_flow_id": "6ab1945e7566f41b5c28e308",
      "version": 10
    }
  }
}

curl -sS https://fabric.wexa.ai/v1/rollback-flow-version \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{"process_flow_id":"6ab1945e7566f41b5c28e308","version":10}'

import { Fabric } from '@wexa-fabric/sdk'

const fabric = new Fabric()
const { result } = await fabric.rollbackFlowVersion({
  process_flow_id: "6ab1945e7566f41b5c28e308",
  version: 10
})

from wexa import Fabric

fabric = Fabric()
out = fabric.rollback_flow_version(process_flow_id="6ab1945e7566f41b5c28e308", version=10)

Errors

Both SDKs raise the same typed errors, chosen from the gateway's own error string first and its HTTP status second. rollback-flow-version checks the fabric:orchestrate.write grant, and reaches the seven classes every tool reaches — listed under the common set. These are the ones specific to it:

Governance

Every call to rollback-flow-version runs through the same ten-stage lifecycle as every other Wexa tool: the credential is resolved to a scope, the fabric:orchestrate.write grant is checked, quota is drawn down, the arguments are validated, policy rules are evaluated, the call is executed, the result is shaped and redacted, and an audit record is written. The lifecycle_id in the response is the handle to that record.

rollback-flow-version is marked consequential, which means it changes something rather than only reading. Two things follow. It is audited in full rather than lightly, and a policy rule may hold it for human approval — in which case the call returns 202 and an ApprovalRequired error carrying the approval id, and the SDKs can wait for the decision and resume rather than making you call again.

See also

The tool index, errors, and which identifier goes where.