Rule History
The history of your rules is part of the Activity log. It has a source called Rules: one row per rule execution with the outcome, rule name, trigger and the number of notifications sent per channel. It is the first place to look for questions like "Why was no notification sent?" or "Did the rule run?".
How to Get There
Three paths lead to the same view:
- Settings → Notifications → History opens the Activity log with the source Rules preselected.
- Dashboard → Evidence → Activity, then pick Rules under Sources in the left menu.
- The red "N failed" badge on a rule in the rules overview and the dashboard card Automation failures lead to the same view, additionally narrowed to the event Rule failed.
Older links to the former address /automation/history redirect to the Activity log automatically. A date range and status carried by such a link are taken over.
What a Row Shows
Each rule execution is one row in the Activity log table:
| Column | Content for rule executions |
|---|---|
| Time | Time of the execution |
| Who | System — a rule fires without an acting person |
| Event | The outcome of the execution (see table below). Underneath, the detail line rule name · trigger · channel counts, for example Missed patrol → email · Patrol missed · Send email ×3 · Send push ×5. If the rule found nobody, it says No recipients. For failed executions the error text appears in red at the end of the detail line |
| Property | The property, if the triggering event knows one; otherwise empty |
The events of the source Rules:
| Event | Meaning |
|---|---|
| Rule executed | The rule ran through completely |
| Rule failed | Permanently failed after five automatic attempts (see below) |
| Rule skipped | Deliberately not executed, e.g. because the rule was disabled in the meantime, the event has no property or there is no shift staffing for the day |
| Duplicate, not sent again | The same event was already being processed and was not executed twice |
| Rule waiting | The execution is waiting for the next processing run, also after Resend |
| Rule running | The execution is running right now |
| Rule scheduled | A delay card is holding the execution; it continues at the scheduled time |
Use the Event filter in the filter row to narrow down to individual outcomes, for example only Rule failed. Use Property to see only the executions for one property. There is no filter for a single rule; use the detail line with the rule name instead.
The Deliveries of an Execution
Clicking a rule row opens a side panel titled with the rule name. The header shows status, trigger and time. The Recipients section lists every single delivery:
- Email, SMS, call: channel icon, recipient (address or phone number), delivery status as a green or red chip, time and, if present, the error text.
- Push and in-app: channel icon and the number of accounts and devices reached ("3 accounts · 5 devices reached"), because these channels are sent in batches.
Below follow the execution details: number of attempts, time of firing, error and the result per action card. If the execution sent nothing, it says "No notifications were sent for this run."
Failed Executions: Signal and Resend
If an execution fails, LiteLog first retries it automatically with increasing intervals. Only after five unsuccessful attempts does it count as permanently failed. That does not stay silent:
- The account's administrators receive an in-app notification ("Automation failed: …").
- In the rules overview the affected rule carries the red "N failed" badge.
- The dashboard card Automation failures counts the failed executions.
The delivery panel of a failed execution has the Resend button in its top right corner. After the confirmation "Retry this run?", LiteLog sets the execution to Rule waiting; the next processing run works it off again and the row in the log then shows the new result. The button only appears on permanently failed executions and only with the permission Edit workflows.
Time Window
- The Activity log shows the last 7 days by default. Use the Date range filter for a different window of at most 31 days.
- Rule executions are deleted after 30 days. Older executions are no longer visible even with a matching date range.
- The export of the Activity log (CSV, PDF, scheduled delivery) knows the source Rules as well and takes over the set filters.
Good to Know
:::tip Note
- Executions of rules that have since been deleted remain visible; the notifications really were sent.
- A running execution (e.g. a waiting escalation chain) always works with the rule state it started with. A rule change in the meantime only affects new events.
- If you want an automatic fallback path on failure instead of resending by hand, connect the red "On failure" output of the action card in the workflow editor.
- The personal inbox under Postfach → Notifications is something different: there each person sees only what went to them. The rule history is the tenant-wide view of all executions. :::
Permissions
:::info Permission The Activity log requires View round evaluation and View persons; accounts with the Customer role have no access. The deliveries in the side panel load with View workflows; Resend requires Edit workflows. The menu item Settings → Notifications → History only appears if you hold both View workflows and View round evaluation. Contact your administrator if you do not have access. :::