Execution history — what really happened
Every execution leaves a result and evidence: which conditions passed and what each action did. This is the only place to see what really happened.
Open Advanced → Automation Logs. There is one entry per execution, with filters for rule, result, order, and date. The view refreshes automatically.
A faster route: the counters beside a rule in the list link to its filtered history.
Results
| Result | Meaning |
|---|---|
| Passed | All actions completed |
| Partial | Some actions failed, but the rule continued |
| Failed | The rule stopped |
| Conditions failed | The event arrived, but the conditions rejected it |
| Waiting | The rule is paused for a delay |
| Skipped | Not executed, for example because another rule was processing the object or retention had removed the order data needed to message its customer |
A waiting entry later changes to the final result; it is not duplicated.
There is a catch with Skipped: it is not in the result filter (which offers All, Passed, Failed, Partial, Conditions failed, and Waiting), even though skipped entries are created. To see them, browse history without a result filter.
Evidence in an entry
Each entry includes details of which conditions passed and failed and what each action did. This answers “why did it not run?” without guesswork.
A message action for a customer whose order data was removed by retention is marked skipped — it is not an error and creates no issue. Messages to the rule’s other recipients, such as a team or manually entered address, are sent as usual.
To see executions rejected by conditions, enable Log failed conditions on the rule. This is useful when tuning a new rule (Create and organize rules).
Diagnosis: “the rule is not working”
- Is there any entry in history?
- No → the event did not occur or the rule is disabled. Check the switch and whether the event actually happens. A new rule may take a short while to be picked up (How a rule runs — queue, retries and waiting).
- Yes → continue.
- Conditions failed → a condition is too restrictive or the data differs from what you expected. Entry details show which condition failed. A condition-check error counts as a failure (Workflow conditions — every listed condition must be met).
- Partial or Failed → see which action failed and read its message. Transient failures are retried; check whether a later attempt succeeded.
- Passed, but nothing happened → check whether you used an action that does nothing despite a successful result (Actions — what a rule can do).
Step four is real and confusing: a “passed” result does not always mean something happened.
How long history is kept
Entries are cleaned once a day according to the retention period set for the rule. Contact NOXTI support to change it.
One reason this matters: successful execution history enforces “Run once.” Clearing old entries may let a rule run again on an object from months ago (Automation pitfalls).
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo