redteam.run_already_finalized
The targeted red-team run is in a terminal `finished` state and no longer accepts state-changing writes.
redteam.run_already_finalized is returned at HTTP 409.
When this fires
Returned when a state-changing call is made against a run that has already been finalized — for example a second finalize attempt, or an append of findings after the run was finalized. Red-team runs are a one-way running -> finished state machine; once finalized, both the run header and its findings rollup are immutable.
What to do
Create a new run with POST /v1/redteam/runs and route subsequent writes there. Branch on this code in your orchestrator to short-circuit retries — the run will never re-open. The TypeScript and Python SDKs surface this as an idempotency-style conflict; treat it the same as any other 409 (do not retry the original request).
See also
- SDK reference — the Python and TypeScript SDKs raise typed exceptions for codes in this namespace.
- Error code index — every code the runtime can return.