Every rule records every check, including the ones that changed nothing. The logs answer two questions: what did this rule do, and why did it not do what I expected.
Open a rule's logs
Go to Paid Media > Ad Automations > Rules.
Find your rule.
Click Logs on its row.
The button is greyed out on a Draft rule, because a draft has never run.
You get one row per check.
Column | What it tells you |
When | The time of the check, in your own timezone |
Result | A plain sentence saying what the check did |
Affected | How many items the check acted on |
Applied Tasks | Which tasks ran |
Optional: filter to Affected Only for just the checks that changed something, or Errors for the ones that failed. The date range defaults to the last 30 days, and you can search by item ID.
A long run of "Nothing matched" is normal
It means the rule is checking and your conditions are not being met. Most healthy rules spend most of their time this way.
What each check result means
You see | It means |
Nothing matched | No item got past the filter. The usual resting state. |
Notified 3 ads, Paused 2 ad sets | The check acted. The verb is the task that ran, the number is how many items it changed. |
Affected 4 ad sets | The check acted, but more than one task ran, so no single verb describes it. |
Nothing was changed | Items matched the filter, but none met the task conditions. |
In progress | The check acted and Meta has not finished applying it. The page refreshes itself. |
Nothing to check | There was nothing at that level on the account to look at. |
Did not run, rule paused | The rule was switched off when its turn came. |
Did not run, Meta limited this ad account | Meta was rate limiting. Nothing was judged and nothing changed. |
The check failed: ... | Something went wrong on Adnova's side. The sentence after the colon is the reason. |
Meta refused this check: ... | Meta was asked and said no. The reason carries Meta's error code, for example |
Two are easy to confuse. Nothing matched means the filter found nobody, so look at your filter. Nothing was changed means it found items and no condition fired, so look at your thresholds.
Look inside one check
Click any row in the list.
Read the table of items.
Optional: switch to Triggered and errors to skip to the items that did something or went wrong.
Two words in the drawer matter.
Applied means the items the filter matched and the rule judged.
Affected means the items it actually acted on.
A check that applied to 5 ad sets and affected 1 is working correctly. The other 4 did not meet the conditions.
Each row shows the value your condition tested, so you can see how close it came. The header says when the numbers were pulled from Ads Manager.
What each item result means
You see | It means |
Affected | The task acted on this item. |
ROAS 0.84, needed above 1 | The item was judged and a condition did not pass. The cell names the metric, the real value, and what your rule wanted. |
This task already acted on this item recently, so it was held by its frequency cap. | The cooldown. The item qualified, but the task's Frequency had used up its turn. |
Waiting for approval | The item matched and the request is in Approvals. Nothing has changed yet. |
In progress | Decided, and another service is still carrying it out. |
Watching only, so nothing was changed | The rule is in watching mode. It reported what it would have done. |
Nothing to change | The item was already in the state the task wanted. |
Already applied by an earlier check | A previous check made this exact change. The account does carry it. |
Rule not running | The rule was switched off while the check was in flight. |
The change did not go through | The action failed. Where Meta gave a reason, it is shown instead. |
A few failures have their own wording. Meta was limiting this ad account is rate limiting, and retries on the next check. Adnova cannot perform this action yet means the action is not supported at that level. Duplicate has its own set, including Meta may have made the copy before the connection was lost, the one case worth checking the ad account by hand before running the rule again.
Common questions
Why does the same item keep saying "frequency cap"? The task's Frequency is holding it back. See How to set what a rule does.
Next
If the rule is not doing what you expect: Troubleshoot: a rule is not doing anything
What has happened to one ad set: How to find out which rule changed an ad set


