An operations dashboard began moving orders into later phases before the work behind those phases had started. A completed receipt could appear as unloading or inspection. A shipped order could still carry the label of an earlier verification phase. The underlying transactions continued, but the …

A database cloned for an upgrade rehearsal began from a valid source snapshot. Later source-side schema and reference-data changes still had to be applied to the test target before application testing could use a comparable baseline.

The target was not empty. It already contained part of the desired …

An automated file delivery produced two copies of the same content at the same destination. Two sibling tasks—separate executions derived from the same parent request—had been created. The first task may have completed the external action, but its user-interface evidence could not prove the final …

A completed automation job is more than a status flag. It may already have created remote objects, read them back, stored quality evidence, and closed a lease. An ordinary retry should therefore be a zero-write operation. Repeating the delivery can duplicate an object or replace evidence that once …

A long-running automation rarely makes every decision in one process. One step creates a plan, later workers produce artifacts, and a retry may resume hours after the original process exited. If those steps repeatedly read a mutable global policy, one logical run can be judged under several rule …

A weekly media pipeline needed to support more than one release in the same ISO week. A simple weekly identifier was no longer unique, so task directories and history records were changed to a versioned form such as 2026-W32-0, 2026-W32-1, and 2026-W32-2.

That solved only half of the problem. A …