Docs
Drift Detection
Drift Detection
Detect when a workflow changes after execution begins and verify that historical runs still match their original definitions.
Workflows evolve over time.
Teams update routing logic, integrations, approvals, and task behavior as operations change.
Drift detection helps teams verify whether a workflow run still matches the version that originally executed.
This is especially useful when teams need to audit historical workflow activity after workflow definitions have changed.
Why drift detection matters
Without drift detection, teams may struggle to answer:
- Did this workflow run against the version we expected?
- Was the workflow changed after execution started?
- Did approvals change after a critical workflow ran?
- Which version of the workflow generated this proof record?
Drift detection helps teams answer those questions with confidence.
How it works
When a workflow begins:
Workflow starts
→ Snapshot captured
→ Definition hash created
→ Workflow executes
→ Workflow changes later
→ Drift verification compares versions