Configuration drift is a difference between the desired workflow version recorded for an environment and the workflow state currently found in that environment.
How drift happens
- Someone edits a workflow directly in the automation runtime.
- A deployment is interrupted or only partially applied.
- A workflow is restored or imported outside the normal promotion path.
- A dependency or platform change alters the runtime representation.
Why drift matters
Unreviewed differences weaken the link between review evidence and production behavior. Drift is not automatically malicious or incorrect, but it needs an owner and a decision.
What a finding should tell you
A drift finding should identify the workflow, environment, expected version, observed state, and detection time. Use the available comparison to determine whether the difference is functional, environmental, or only representational.
Three possible outcomes
- Investigate: keep the finding open while you determine the source and impact.
- Accept runtime: review the runtime change and promote it into the approved desired-state process.
- Restore desired state: reapply the approved version using your authorized recovery procedure.
Do not dismiss a finding simply to clear the dashboard. Record why the chosen state is correct and verify the environment after reconciliation.