A workflow that does not show the expected version may be waiting for an action, actively deploying, drifted, or unable to synchronize. Identify its state before retrying.
Confirm what you expected
- The workflow and target environment
- The expected version or commit
- The deployment or promotion that should have applied it
- The time the action was submitted
Read the current state
A pending or approval state may require an authorized decision. An in-progress state should be allowed to complete. A failed state needs its error details. A drift finding means the runtime differs from desired state and requires review rather than a blind retry.
Check related records
- Open the deployment record and confirm its target and result.
- Review the latest audit event for the workflow.
- Check the environment connection.
- Review any drift finding or version comparison.
- Confirm required credential references exist in the target.
Avoid duplicate actions
Do not repeatedly submit the same deployment while its result is unknown. Preserve the original deployment and correlation identifiers so support can follow the sequence.
Escalate
Provide safe workflow, version, environment, deployment, audit-event, and error identifiers with timestamps. Describe the expected state and the state displayed. Do not include workflow payload data or secret values unless an approved secure support process specifically requires it.