Dry run
Every rule has a Dry run button. It replays the rule against the last 30 days of activity and lists exactly which tasks would have been touched and how — without changing one of them. Read that list before you enable anything that assigns, moves or notifies.
The audit log
Automations → Activity shows every run: what fired it, which conditions passed, what changed, and how long it took. A rule that did nothing appears too, with the condition that stopped it — which is usually the answer to "why did my automation not run?"
Loop protection
A rule cannot trigger itself, and a chain stops after ten hops. If two rules keep waking each other, both are paused and the owner is notified rather than the workspace running in circles.
Actions taken by an automation are attributed to the rule, not to a person, so the task history stays readable.
Did this answer your question?
If not, write to support and quote this page. Median first reply is under two hours on weekdays.