flow-versions
List a process flow's promoted versions, newest first, with which one is live. Each version is a snapshot of the WHOLE flow taken when it was promoted — every agent, its config, and the wiring — so it captures structural changes (agents added, rewired, removed) that per-agent versions cannot. Status is promoted | superseded | rolled_back; live_version is authoritative and is NOT necessarily the highest number, because a rollback makes an earlier version live again without renumbering. Promote with promote-flow; change which is live with rollback-flow-version.
What it is called on each surface
The wire name is flow-versions everywhere: it is what the Wexa MCP server advertises, the REST path is
POST /v1/flow-versions, and each SDK exposes it under its own language's naming convention.
| Surface | Name |
|---|---|
| Wexa MCP server | flow-versions |
| REST API | POST /v1/flow-versions |
| TypeScript SDK | fabric.flowVersions() |
| Python SDK | fabric.flow_versions() |
Arguments
1 of the 2 arguments is required. Omitting a required one is refused before the tool runs, at the validation stage, so it costs nothing and changes nothing.
| Argument | Type | Required | Notes |
|---|---|---|---|
include_snapshot | boolean | Optional | Include each version's full flow snapshot (large). Default false — the list is for choosing a version, not reading one. |
process_flow_id | string | Required | Process flow id. Required. |
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 flow-versions:
{
"content": [
{
"type": "text",
"text": "{\"lifecycle_id\":\"qlc_000180\",\"result\":{\"live_version\":1,\"process_flow_id\":\"6ab1945e7566f41b5c28e308\",\"versions\":[{\"id\":\"fver_c9593de3-f85c-48bb-bf39-32c923cf467e\",\"agentflowId\":\"6ab1945e7566f41b5c28e308\",\"version\":1,\"status\":\"promoted\",\"agentCount\":0,\"promotedBy\":\"6a79a770b6c128ccc24bfca7\",\"promotedAt\":\"2026-09-21T20:32:39.381Z\"}]}}"
}
],
"isError": false
}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": "flow-versions",
"arguments": {
"process_flow_id": "6ab1945e7566f41b5c28e308"
}
}
}Errors
Both SDKs raise the same typed errors, chosen from the gateway's own error string first and its
HTTP status second. flow-versions checks the fabric:orchestrate.read grant, and reaches the seven classes every
tool reaches — listed under the common set. These are the ones specific to it:
| Error | Status | Raised when |
|---|---|---|
NotFound | 404 | process_flow_id matches no process flow in this project, or that flow has no version history yet. |
ConfigurationError | 5xx | flow-versions is not available to you. Retrying will not help. |
Governance
Every call to flow-versions runs through the same ten-stage lifecycle as every other Wexa tool: the
credential is resolved to a scope, the fabric:orchestrate.read 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.
flow-versions only reads, so it is not marked consequential: it is audited lightly and is never held for
approval. It still consumes quota and is still refused by policy like anything else.