What is dry-run and why use it?
Updated Oct 5, 2026
Dry-run answers "what would this rule have done?" using your last 20 tickets. You see which tickets matched, which conditions passed, and which actions would have fired — while nothing actually happens: no comments are posted, no emails sent, no webhooks fired, no AI calls made, no status changed. Use it while drafting a rule (Test rule button) or against a saved rule before re-enabling it after edits.
Reading the result
0 matches usually means a condition contradicts the trigger — check operators like is-one-of.
Surprising matches usually mean a condition is too broad — tighten with AND conditions.
Skipped actions appear with reasons (rate cap, inactive member, deleted snippet) exactly as they would live.
Was this helpful?
Share