Execution Proofs

Execution proofs help teams verify exactly what happened during a workflow run.

They create a verifiable record of workflow execution that can be reviewed later for troubleshooting, audits, compliance reviews, and operational verification.

Instead of relying only on logs, teams can use proof records to validate workflow outcomes with stronger confidence.

Why teams use execution proofs

Execution proofs help answer questions such as:

• What workflow ran?
• Which version of the workflow executed?
• What tasks completed?
• What failed?
• What outputs were generated?
• Were retries triggered?
• Can this run be independently verified later?

These records help teams maintain operational trust across critical workflows.

What gets captured

Execution proofs can include:

• workflow identifiers
• workflow snapshots
• execution timestamps
• task outputs
• retry attempts
• failure states
• execution metadata
• verification references

This helps teams review workflow activity after execution completes.

Example proof record

A workflow proof may look like:

{
  "workflowRunId": "clx123run0000000000000000",
  "workflowId": "clx456wf0000000000000000",
  "workflowDefinitionSnapshotId": "clx789snap00000000000000",
  "definitionHash": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
  "finalStatus": "SUCCESS",
  "completedAt": "2026-04-27T18:41:52.931Z",
  "context": {
    "ticketId": "INC-8842",
    "severity": "SEV2"
  },
  "tasks": [
    {
      "nodeKey": "normalize",
      "status": "SUCCESS",
      "attempt": 1
    },
    {
      "nodeKey": "notify_slack",
      "status": "SUCCESS",
      "attempt": 1
    }
  ]
}