An automation needs a condition that becomes false after it acts, or a supported one-time condition. A guard tag is useful when the action adds that same tag. Without a nullifier, the next hourly sweep can repeat an unwanted action. Greater-than time conditions survive a missed sweep better than a narrow exact-hour window. Inspect repeated-sweep evidence, because the first successful run alone cannot establish that the workflow is safe to repeat.
Use the supplied training clock rather than waiting in real time. Inspect an eligible ticket and a nearby exclusion after advancing the scheduler. Later requests remove the worked sequence and change the threshold. The result needs both the intended saved effect and evidence that an unsafe repeat is prevented.
Worked example: nullifying automation conditions.