Delete Resolution

Permanently delete a resolution run and its per-document results with DELETE /v1/resolutions/{id}. The source job run and its extracted data are unaffected.

Delete a resolution run and all its associated result rows permanently. The delete cascades: every per-document result created for the run is removed along with the run row itself, including the frozen policy_snapshot that recorded which configuration produced those results. The originating job run, its documents, and its extracted values are not touched.

Use deletion to clean up abandoned experiments and stale runs. For a failed run you intend to retry, deletion is usually the wrong tool: [POST /v1/resolutions/{id}/execute](execute-resolution) re-executes the failed run in place, skipping documents that already completed. Delete-and-recreate is only preferable when you want the new run to pick up configuration changes, since the snapshot is frozen at creation time.

Deleting a run that is currently processing removes the run and its results immediately, but does not gracefully stop work already in flight — background batches may error harmlessly as they find their run gone. Prefer waiting for a terminal status (completed or failed) before deleting, so you are never racing the executor.

Deletion is irreversible, but cheap to recover from in practice: because the source job run keeps all its extracted data, recreating the same resolution is one POST /v1/resolutions call with the same source_run_id — the new run simply snapshots whatever configuration is current at that moment, and gets a fresh UUID.

The response is minimal — { "deleted": true } with status 200 — and the effect is immediate: subsequent GET /v1/resolutions/{id} calls return 404 and the run no longer appears in the [list](list-resolutions). There is no bulk delete; to sweep a workspace, list runs with ?status=failed and delete them one by one. The endpoint requires write scope and only ever sees your own organization's runs — a foreign UUID is indistinguishable from a missing one (both 404).

curl -s -X DELETE https://api.talonic.com/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890 \
  -H "Authorization: Bearer tlnc_your_api_key"

Response

{
  "deleted": true
}

Errors