Question
Automations that fail loudly get fixed. Automations that return nothing look like a quiet week. The three usual causes are an unpopulated trigger field, criteria so narrow nothing matches, and nobody ever verifying it fired.
The workflow enrolls on a field that reps do not fill in, or that only a sync populates on some records. It is technically correct and matches nothing.
Check the field fill rate before checking the logic.
Four conditions ANDed together, each reasonable, together matching two records a quarter. This is the most common version and it never announces itself.
Run each condition separately and count what matches. One of them is usually the problem.
Built, tested once on a record that happened to match, shipped, never checked again. Six months later somebody notices the alerts stopped, and they never started.
Deliberately break it and confirm the failure appears. If removing a condition does not change the output, the workflow was not doing what you thought.
Then set a reminder to check the fire count monthly. An automation with no monitoring is an automation you will find broken by accident.
Questions
Most often the enrollment field is not populated on the records you expect, or several criteria combined match almost nothing. Test each condition separately and count matches.
Break it deliberately and confirm the failure shows up. If removing a condition does not change the output, it was never doing what you assumed.
It arrives in Slack
Every morning, each rep gets one message naming the deals on their own book that moved overnight, biggest mover first, with the reason beside each number and the deals that have gone quiet underneath.
$99 a month, cancel any time.. Everyone on the team. No per seat charge. Connect a CRM and it runs. No implementation fee. 14 day trial. No card.
Related reading
Every CRM can post to Slack, and almost none of it gets read: the alerts fire on field changes rather than on anything meaningful. What to send instead.
The handful of data problems that quietly break forecasting, reporting and any scoring model built on top. What to check and in what order.
GTM engineering is the newest title in revenue teams and the least clearly defined. What the job actually covers and how it differs from RevOps.
Top down division of a board number produces quotas nobody believes. The bottom up version and how to reconcile the two.
Reviewed September 20, 2026 against the product as it behaves today.