History
Under Automation → History you see every execution of your rules from the last 30 days: when which rule fired, with which result, and who was notified. It is the first place to look for questions like "Why was no notification sent?" or "Did the rule run?".
Feature Overview
The list
Each row shows the time, the rule (system rules are marked), the trigger, the notifications sent per channel, the status, and — if present — the error. Clicking the row opens the detail with the actual recipients: emails with their real delivery status, SMS and calls with the phone numbers, push and in-app as counts.
You filter by date range, rule, and status:
| Status | Meaning |
|---|---|
| Success | The rule ran through completely |
| Scheduled | A delay card is holding the execution — it continues at the scheduled time |
| Pending / Running | The execution is waiting for the next processing run or is running right now |
| Failed | Permanently failed after five automatic attempts (see below) |
| Skipped | Deliberately not executed — e.g. the rule was disabled in the meantime or is no longer covered by the package |
| Duplicate | The same event was already being processed and was not executed twice |
Failed executions: signal and retry
If an execution fails, LiteLog first retries it automatically with increasing intervals. Only after five unsuccessful attempts does it count as permanently failed — and that does not stay silent:
- The account's administrators receive an in-app notification ("Automation failed: …").
- In the rules overview the affected rule carries a red "N failed" badge; clicking it leads here.
In the history you then restart the execution with the "Run again" button on the row. The retry resumes at the point of failure — steps that already went out are not sent twice. The button only appears on permanently failed executions.
Good to Know
:::tip Note
- The history goes back 30 days; older entries are removed automatically.
- 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 retrying manually), connect the red "On failure" output of the action card in the workflow editor. :::
Permissions
:::info Permission Viewing the history requires View workflows; retrying an execution requires Edit workflows. Contact your administrator if you do not have access. :::