Automation Rule Execution History in IZI
Automation Rule Execution History in IZI
Section titled “Automation Rule Execution History in IZI”The execution history is a log of every time an automation rule was evaluated and executed (or not). It is the primary diagnostic tool: if a bonus was not accrued or a notification was not received — the answer is here.
Where to find it
Section titled “Where to find it”Automation → open the rule → History tab.
Entries are in reverse chronological order: newest at the top.
What each entry contains
Section titled “What each entry contains”| Field | What it shows |
|---|---|
| Date and time | When the trigger event occurred |
| Client | Who performed the action (name, phone) |
| Status | Result of rule execution |
| Details | More information — especially important for “Error” status |
Execution statuses
Section titled “Execution statuses”Completed
Section titled “Completed”The event occurred, conditions were met, all actions finished successfully. If the action was a bonus accrual, the funds are already in the client’s bonus account. If it was a notification, it has been sent to the app.
Skipped
Section titled “Skipped”The event occurred but conditions were not met — the rule intentionally did not run. This is normal filtering behavior, not an error.
Example: a rule fires on top-ups from 500, the client topped up 200 — entry reads “Skipped” with the specific condition that was not met.
The event occurred, conditions were met, but something went wrong while executing one of the actions. Execution stops at the first failing action — subsequent actions do not run.
Open the entry — the details will specify which action failed and why.
Diagnosing by status
Section titled “Diagnosing by status”Expected “Completed” — got “Skipped”
Section titled “Expected “Completed” — got “Skipped””The rule saw the event but conditions did not pass. Check:
- Open the entry → see which condition was not met
- Compare with the current rule settings — the threshold may be too high
- Check the client’s parameters: actual hours/spending/balance in the client profile
More on condition setup → Rule conditions.
”Error” status
Section titled “”Error” status”- Open the entry → read the error description
- Common causes:
- The bonus formula produced a negative or zero value
- The group specified in the action was deleted
- A technical failure when sending the notification
- After fixing the issue, verify operation on the next event
No entries for this client in the history
Section titled “No entries for this client in the history”The rule never saw the event for this client. Check:
- The rule is active (toggle is on)
- The client’s club is within the rule’s scope (Clubs field in the rule settings)
- The event actually occurred — verify in the transaction history or in the client profile
No entries at all
Section titled “No entries at all”The rule has never fired. Either:
- The rule was just created and no matching events have occurred yet
- The rule is not active
- The scope is limited to clubs where no events have happened
Connection with the client profile
Section titled “Connection with the client profile”Automation accruals appear in the client’s profile — in the bonus account history, each transaction is labeled with its source (“accrued by automation”). This lets you see not just “bonus accrued” but which specific rule triggered it.
Managing a client’s balance → Manage client balance.
See also
Section titled “See also”Frequently asked questions
Where do I find the execution history for a specific rule?
Go to Automation → open the rule → History tab. All executions are listed in chronological order with the client, date, and status.
What does the 'Skipped' status mean?
The event occurred, the rule detected it, but conditions were not met — so the actions did not run. This is normal rule behavior, not an error. For example, a client topped up their balance but the amount was below the threshold condition.
Is the history stored indefinitely?
History is retained according to the organization's data retention settings. For diagnostics, look at recent executions — older records are less relevant to current configuration.
Can I see execution history for a specific client?
Yes — the client's profile in the Clients section shows a transaction history including bonus accruals from automation. In the rule's history itself, you can filter by client.