Meta ads automated rules not working: why they do not fire
Troubleshooting guide · 2 min read · Updated 2026-10-21 · By the Cofoundr team
Rules usually fail quietly for ordinary reasons: the condition never becomes true in the time window you chose, the rule is scoped to the wrong objects, it checks too rarely for the problem it targets, or it conflicts with another rule. Read the rule's own history first, then simplify the condition, then test it in notify-only mode.
Automated rules are a good idea and an easy thing to get slightly wrong. A rule that never fires looks the same as a rule that has nothing to do, so problems can go unnoticed for weeks. This guide gives you a short debugging order, and a safer way to build rules you can trust.
1. Read the rule's history
Start where Meta shows what the rule did and when it last ran. If it ran and found nothing, the condition did not match. If it never ran, check its schedule, scope and status.
2. Check the condition and its time window
- A rule on cost per result over today only can never fire early in the morning, when there is little data.
- A lifetime window can hide a recent problem inside a long, healthy history.
- Several conditions joined together all have to be true at once. Test each alone.
- Check the metric: some metrics are reported with a delay, so the rule sees older numbers than you do.
3. Check scope
- Is the rule applied to the right campaigns, ad sets or ads?
- Does it include paused objects it can never change?
- Did you add new campaigns after creating the rule? Check whether they are covered.
4. Check how often it runs
Meta runs rules on a schedule it controls, with options for how often depending on the rule type. A problem that develops and ends between checks can be missed. Check Meta's current help pages for the options, and choose the most frequent one that suits the job.
5. Look for conflicts
A rule that pauses an ad set and another that turns it back on, or a scaling rule that keeps raising a budget a second rule keeps lowering, will fight. Keep rules few, with one clear purpose each, and record what each is for.
6. Test in notify-only mode first
Run a new rule so it only tells you what it would have done. When its alerts look right for a week, let it act. This is the safest way to build trust in an automation, and a good habit for clients too. See safe automation.
How Cofoundr approaches rules
Cofoundr runs its own rules across all your accounts: pause ad sets that waste money, scale a winning campaign, alert on a spend spike and pause weak creatives. Each rule can be set to alert only or to act. Rules only check active campaigns, have cooldowns so a change is not repeated straight away, and every action is logged with its reason and result, so you can see what ran and why. You choose when they run, including scheduled runs.
Frequently asked questions
Why is my Facebook automated rule not running?
Check the rule's history for its last run, then its schedule, scope and status. If it ran and found nothing, the condition probably never matched in the time window you chose.
Can automated rules lose me money?
A badly built rule can, for example by pausing good ad sets on thin data or scaling a budget too fast. Test in notify-only mode, use sensible time windows and keep rules few.
How often should rules run?
As often as the problem needs. A spend problem should be checked often, while a weekly performance review does not need hourly checks.