How to manage rules and view run history

Last updated June 10, 2026

Once you've built a few automated rules, the rules panel becomes your control center: turn rules on or off, edit their conditions, run everything on demand, and audit exactly what each run changed. This guide covers every action in that panel.

To open it, go to the ads manager and open Automated rules. The list shows every rule on the currently selected ad account, with its schedule, a plain-English summary, and when it last ran.

Enabling or disabling a rule without deleting it

Each rule has a toggle switch next to it. Flip it off and the rule stays in your list, keeps all of its conditions and history, but stops running on its schedule. Flip it back on whenever you want — nothing is lost.

Disabled rules never run automatically. The toggle is the safe way to "pause" a rule you might want again.
Run all now only triggers rules that are currently enabled, so a disabled rule is skipped there too.
You can also toggle Enabled from inside the rule editor.

This is the right move when a rule is too aggressive or you're testing something temporarily. There's no need to delete and rebuild.

Editing or deleting an existing rule

To change a rule, click the pencil (Edit) icon on its row. This opens the same builder you used to create it, pre-filled with the rule's current level, conditions, action, schedule and budget guardrails. Adjust anything, then click Save changes.

A few things to know while editing:

Schedule times are shown in your local time zone, even though the scheduler runs in UTC behind the scenes — uplads converts automatically.
Editing a rule does not erase its run history. Past runs stay in the log under the rule's name.

To remove a rule entirely, click the trash (Delete) icon on its row. Deletion is immediate and removes the rule from the account. If you only want to stop it temporarily, disable it instead.

Running all rules manually right now

Click Run all now at the top of the list to evaluate your rules immediately instead of waiting for their schedule.

uplads runs every enabled rule on the selected ad account once.
Each rule checks its conditions against live Meta data and applies its action to matching campaigns, ad sets or ads.
You get a toast confirming how many rules ran and how many actions were applied, e.g. "Ran 3 rule(s), applied 7 action(s)."

This is useful for testing a freshly built rule or forcing a check after a big change. The action is safe to repeat — re-pausing an already-paused ad is a no-op, so running twice won't double-apply. Manual runs are logged exactly like scheduled ones, tagged as triggered manually.

Reviewing run history (matched entities and applied action)

Click the run history (scroll) icon on any rule to open its log. Each run is a collapsible card — the most recent one is expanded by default, older ones stay collapsed so a year of daily runs doesn't flood the view. uplads keeps full history (loaded up to 500 most recent runs), not just the last handful.

Every run card shows at-a-glance badges: matched, changed, skipped and failed. Expand a run to see the entities grouped by campaign, with for each one:

The exact entity (Campaign, Ad Set or Ad) and its name, with a link to open it in Meta Ads Manager.
The concrete change — ACTIVE → PAUSED for status rules, or €50.00 → €60.00 for budget rules.
A metric snapshot at the moment the rule fired (spend, ROAS, CTR, etc.), so you can see why it matched.
Already in target state entries — matched but no change was needed (e.g. already paused).
Failed entries with the error message, if Meta rejected a change.

If a run matched nothing, the card says so plainly: no campaigns, ad sets or ads were touched. This makes it easy to audit every automated action after the fact, or confirm a rule is working before you trust it on a schedule.

How rule notifications are deduped and rate-limited

When a rule matches at least one entity, uplads sends a notification through the channels you enabled for Automated rule matches in Configuration → Notifications (email, Slack, ClickUp). To keep your inbox sane, several guards apply automatically:

Disabled channels are skipped. If rule emails are turned off, no email is sent — the attempt is just logged.
Concurrent-tick dedup. If the same rule somehow fires twice within 30 seconds (e.g. an overlapping scheduler tick), the second notification is suppressed so you don't get duplicates.
Per-rule hourly cap. Each rule has a maximum number of notifications per hour. Once it's hit, further matches that hour are recorded but not re-sent.
Honest counts. The notification reports what actually changed, not just what matched — so it never claims "paused 15" when 9 of those were already paused.

These limits apply identically whether the rule ran on schedule or via Run all now. The notify action follows the same channel settings: if none are enabled, the match is still recorded in the rule's run log.