Most of the time when something feels broken in the CRM, nothing is actually broken. Two settings that are supposed to agree with each other quietly disagree, and the automation does exactly what you told it to do, which unfortunately is not what you meant. This chapter is a checklist for the handful of mismatches that cause almost every "why didn't it fire?" question.
The CRM is rarely wrong. It is usually two settings, in two different places, that were set at different times by different people, and never compared side by side.
The golden rule: stage is the most common trigger
Stage change is the most common trigger in the CRM, but it is not the only one. Automations can also fire on form submissions, property updates, meetings booked, tags added, and more. The golden rule is: whatever the trigger is, make sure it actually happens. When an automation does not fire, the first question is never "is the automation broken?" It is "did the trigger event actually occur, and did it match exactly what the automation is listening for?" In the case of stage-change automations, three different places set or watch stage. All three have to agree.
Try changing the three dropdowns above. When all three line up, the parent gets their email. When any one of them disagrees, the automation goes quiet, and you spend an hour wondering why.
Walkthrough: a tour was booked but nothing happened
This one is sneaky. A parent books a tour, they are in the CRM, but the confirmation email never arrives. You open the automation and it says "Completed." Nothing looks broken. The hidden cause is often a safety switch that stops the same lead from running through the same automation twice.
The filter flip: 'is equal to' vs 'is not equal to'
This one trips up almost everyone at least once. You are setting a filter on an automation, your brain reads the sentence one way, and you pick the operator that sounds right but means the opposite. Try it: flip the operator below and watch which leads actually make it through.
- Jamie R.Website
- Alex T.Website
- Sam Q.Website
- Priya M.Referral
- Devon K.Walk-in
- Morgan L.Referral
Read the lead's profile before you change anything
Every lead has their own profile, and that profile tells you exactly what happened, including the quiet settings that silently block automations from doing their job. Before you change anything in Forms or Automations, open the lead's profile and check the little flags that sit next to the big timeline.
Other things that look broken but aren't
A debugging mindset that will save you hours
Still stuck?
Try the "Fix" button inside the automation editor first, it will flag obvious gaps like a missing email address or a deleted stage. If it still does not add up, reach out to Playground support with the lead's name and the automation name. They can read the same timeline you can, plus the bits you cannot see.