Lesson 7 of 8 · 8 min

Monitoring automations

Reading run history to track and debug automations.

Lesson 7 of 8

Every automation run is recorded. This lesson shows where that history lives — the monitoring summary on the Automations page and the per-rule 'View logs' dialog — and how to use it to debug failures.

Before you start

  • Manager access or above ('manage automations')
  • At least one automation that has run (or been tested)

Monitoring lives on the Automations page

There is no separate 'Logs' area. The Automations page itself carries a monitoring summary — cards for Recent runs, Completed (with a success rate), Failed, Skipped, and Average duration — and a 'Recent automation runs' feed underneath the rules table. Each rule's row also shows its last run status and time.

Per-rule execution logs

Every rule has a 'View logs' button (in its row on the list, and again inside the editor) that opens the 'Execution Logs' dialog. It lists each run with a status — completed, failed, running, or skipped — plus duration, the trigger, the related matter, any error message, and a per-action breakdown. Skipped runs explain that the action's conditions weren't met.

Debugging failures

When a run fails, the log shows exactly which action failed and the error message — a missing field, a permission problem, or an unreachable service. Fix the cause and re-run: for a Manual trigger use 'Run Now', or use 'Test with sample matter' in the editor to dry-run against sample data.

  1. 1

    Scan the monitoring summary

    On Settings > Automations, the summary cards (Recent runs, Completed, Failed, Skipped, Average duration) give an at-a-glance health check, and the 'Recent automation runs' feed lists the latest executions with their action results. Use this to spot a rule that's failing or being skipped more than expected.

  2. 2

    Open a rule's execution logs

    Click 'View logs' on any rule to open the 'Execution Logs' dialog. Each entry shows its status (completed / failed / running / skipped), duration, trigger, and per-action results; failed runs include the error message and skipped actions explain why their conditions weren't met.

Tips & pitfalls

  • A 'Skipped' status is not an error — it means the automation (or one of its actions) was triggered but its conditions weren't met, so it was intentionally not run.
  • To see how a rule behaves without waiting for a real event, use 'Test with sample matter' in the editor — it runs the rule against sample data and records the result in the logs.

Key takeaways

  • Monitoring lives on the Automations page — summary cards plus a 'Recent automation runs' feed
  • Each rule's 'View logs' opens an 'Execution Logs' dialog with status, duration, errors, and per-action results
  • There is no separate 'Logs' sub-navigation
Chaining automations Templates and packs

Put the lesson into practice.

Book a guided session and our team will help you configure MatterFirst for your own practice.

Book a session Back to the Academy