Rule Execution History and Troubleshooting
Last updated: April 18, 2026
Every time an automation rule runs in Wevion, it creates a detailed execution record. The execution history gives you full visibility into what happened, which entities were affected, what actions were taken, and why some entities were skipped. This article explains how to read and use execution history to keep your automation running smoothly.
Prerequisites
- At least one automation rule created in Wevion.
- The rule must have executed at least once (either on schedule or manually triggered).
How to View Execution History
- Navigate to Automation > Rules from the sidebar.
- Click on the rule you want to inspect.
- Select the Execution History tab (or scroll to the Executions section, depending on your layout).
The history is paginated. Each page shows a batch of executions, ordered from most recent to oldest. Use the page controls at the bottom to navigate through older runs.
Understanding the Execution Summary
Each execution entry shows a high-level summary before you drill into details.
Status
Every execution has one of these statuses:
| Status | Meaning |
|---|---|
| Success | The rule ran to completion. Actions were attempted on all matched entities. |
| Partial | The rule ran but some entities encountered errors while others succeeded. |
| Failed | The rule encountered a critical error and could not complete. |
| No Match | The rule ran successfully but no entities met the conditions. |
Summary Counters
| Counter | What It Tells You |
|---|---|
| Entities Evaluated | Total number of campaigns, ad sets, or ads that fell within the rule's scope |
| Entities Matched | How many met the rule's conditions |
| Entities Acted | How many entities had their action successfully executed (e.g., budget changed, status paused) |
| Entities Skipped | How many matched the conditions but were not acted upon, along with the reason |
Timing
- Started At — when the execution began
- Completed At — when it finished
- Duration (ms) — total execution time in milliseconds
A typical execution completes in under a few seconds. If you see durations exceeding 30 seconds, the rule may be evaluating a very large number of entities.
Reading the Details Array
Click on any execution to expand its details. Each evaluated entity has a row with:
| Field | Description |
|---|---|
| Entity ID | The Meta ID of the campaign, ad set, or ad |
| Entity Name | The human-readable name |
| Action | What the rule attempted (e.g., "pause", "increase_budget_20%", "decrease_bid_10%") |
| Before Value | The value before the action (e.g., daily budget was $50) |
| After Value | The value after the action (e.g., daily budget changed to $60) |
| Metrics | The metric snapshot at evaluation time (CPA, ROAS, CTR, spend, etc.) |
| Skipped Reason | If the entity was skipped, the reason why (see below) |
| Error | If the action failed, the error message |
Understanding Skipped Reasons
When an entity matches your conditions but is not acted upon, Wevion records a skipped reason. There are three:
Cooldown
This entity was already acted upon recently and the cooldown period has not elapsed. Cooldown prevents rules from stacking repeated changes before you can evaluate the impact. To act more frequently, reduce the cooldown setting on the rule.
No Tokens
The Meta API token for the ad account has expired or been revoked. Navigate to Settings > Connected Accounts and reconnect the affected account. The rule will act on the next scheduled run after the token is refreshed.
Reconnecting a Meta Ad Account
Failure Backoff
A previous attempt to act on this entity failed (Meta API error), and Wevion is waiting before retrying. Check the error field from the previous execution to understand the root cause. Common causes: Meta policy restrictions, rate limiting, or the entity being in a non-modifiable state (e.g., under review). The rule will retry automatically after the backoff period.
Troubleshooting Common Issues
"My rule is not firing"
- Check if the rule is active. Navigate to the rule and verify its status is "Active", not "Paused".
- Check the execution history. If there are no recent executions, the rule's schedule may not have triggered yet. Verify the rule's schedule or frequency setting.
- Check the "Entities Evaluated" counter. If it shows 0, the rule's scope (ad accounts, entity filter) may be excluding everything.
- Check the "Entities Matched" counter. If entities are being evaluated but none match, your conditions may be too strict. Use the Preview feature to test your conditions against live data.
Rule Preview (Dry-Run) — Test Before You Activate
"Entities are being skipped every run"
- Check the skipped reason. Expand the execution detail and look at the "Skipped Reason" column.
- If cooldown: Your rule is running more frequently than the cooldown allows. Either increase the run interval or decrease the cooldown period.
- If no_tokens: Reconnect your Meta account immediately. Until the token is refreshed, no actions can be executed.
- If failure_backoff: Investigate the original error from the previous execution. The backoff will clear automatically once enough time passes.
"The rule matched entities I did not expect"
- Review your conditions. Pay particular attention to the condition logic (AND vs OR). With OR logic, an entity only needs to meet one condition to match.
- Check the lookback period. A 7-day lookback averages metrics differently than a 1-day lookback. An entity might have a high average CPA over 7 days even if today's CPA is fine.
- Use Preview mode. Run a dry-run to see the current match list and the specific metric values that triggered each match.
"Actions are failing with errors"
- Expand the execution detail and read the error messages.
- Common Meta API errors: "Budget amount is too low" (below Meta's minimum), "Cannot update entity" (entity under review or deleted), "Rate limit exceeded" (too many API calls — backoff handles this automatically).
- Check token validity. An expired token produces authentication errors across all entities in that account.
Using Rule Stats for a Quick Overview
For a bird's-eye view of your entire automation setup, navigate to Automation > Rules and check the stats bar at the top of the page. This shows:
| Stat | What It Shows |
|---|---|
| Total Rules | How many rules you have created (active and paused combined) |
| Active Rules | How many are currently enabled and running on schedule |
| Executions Today | Total number of rule executions across all rules since midnight |
| Actions Today | Total number of successful actions taken across all rules today |
| Errors Today | Total number of failed actions today |
If "Errors Today" is unexpectedly high, drill into the individual rules' execution histories to identify the source.
Tips and Best Practices
- Check execution history after activating a new rule. Verify that the first few runs match your expectations.
- Monitor the errors counter in rule stats daily. A spike often indicates an expired token or Meta API issue.
- Use Preview before modifying an active rule. Even small condition changes can shift match behavior.
Rule Preview (Dry-Run) — Test Before You Activate
FAQ
Q: How long is execution history retained? A: Execution records are retained indefinitely. There is no automatic expiration on stored executions. You can page through older executions at any time.
Q: Does a "No Match" execution mean something is wrong? A: Not necessarily. It means no entities met the conditions when the rule ran. For anomaly-catching rules (e.g., CPA above a high threshold), "No Match" is the expected result most of the time.
Q: How do I know if a rule's action reached Meta? A: Check the "After Value" in the execution detail. If it shows the updated value and no error is present, the change was sent to Meta successfully.