Execution timing
Triggers react to ticket creation or updates. Automations use elapsed-time conditions and run hourly on nonclosed tickets. An hourly run need not start at minute zero. A saved field edit is not an instruction to execute every automation immediately.
Trigger re-evaluation
Take two original rules. Rule A sets High when review_needed is present. Rule B adds that tag to a Normal-priority Billing ticket. A starts above B and initially fails. After B changes the ticket, evaluation restarts and A can become true. A rule already fired in the update cycle does not fire again in that cycle.
Inspect saved field changes and the audit, not only the rule list. A later conflicting rule may still replace an intended value. Use specific source conditions and avoid contradictory effects.
One-time automation
For a Pending ticket older than 24 hours, require the absence of followup_done, then add that tag when the automation acts. The action cancels a condition. A greater-than or at-least threshold avoids depending on one exact-hour window.
In the local course, you advance an explicit practice sweep and inspect the second run. The deterministic clock models the boundary; it does not prove a production scheduler ran. Continue with SLA policies to see how updated ticket fields affect policy selection.