Order Daemon records every rule execution automatically. If a rule fires, the log shows it. If a rule was skipped because a condition failed, the log shows that too, along with which condition blocked it. You do not need to enable logging or configure anything; it runs from the moment rules are active.

The two monitoring tools

Insight Dashboard is your primary view into rule activity. It shows every execution event across all rules, filterable by rule, status, date, and order. Each log entry shows the trigger that fired, whether conditions passed or failed, which action ran, and any errors. The condition failure detail is particularly useful during setup, since it tells you exactly which check blocked the rule rather than just that the rule did not run.

Diagnostics Dashboard runs automated health checks against your environment. It checks that required WooCommerce hooks are firing correctly, that the database tables Order Daemon needs are present and writable, and that there are no conflicts with other plugins affecting order status transitions. Run Diagnostics when rule execution looks correct in the Insight Dashboard but outcomes are still not appearing in WooCommerce.

The debugging flow

When a rule is not behaving as expected, work through this sequence.

1. Open the Insight Dashboard and filter by the rule in question
2. Find the most recent execution attempt for the relevant order
3. If the entry shows conditions failed, expand it to see which condition blocked the rule
4. Fix the condition configuration, or check whether the order data matches what you intended to filter on
5. If there is no execution entry at all, the trigger is not firing, which is an environment issue rather than a rule configuration issue
6. Run the Diagnostics Dashboard to check for hook conflicts or missing database tables

Example: your auto-complete rule for digital orders is not running. Open the Insight Dashboard and filter by that rule. If the last few executions show a condition failure, click through to see the detail. A common cause is the virtual product condition being set to “all items” when the order also contains a fee line. Adjusting the condition or the order structure resolves it immediately. If there are no execution entries for orders you expected to match, go to Diagnostics and check the order status hook report.

Tip: The condition failure detail uses the same language as the Rule Builder, so the field names in the log match exactly what you configured.

Child docs in this section

• The Insight Dashboard covers the execution log in full, including filtering, bulk actions, and log retention
• Diagnostics Dashboard covers every automated health check and what to do when one fails