Connected tools / GUIDE + WORKSHEET
What to monitor after an automation goes live
Monitor business outcomes, missing events, stale data, and exceptions with a practical automation monitoring checklist.
THE STARTING POINT
Monitor the business result as well as technical errors. Check whether expected work arrived, whether destination records are current, and whether exceptions have an owner. A workflow that runs successfully but processes no events or writes the wrong values can still be broken.
Define normal before defining alerts
Document what the workflow should do, how often events normally arrive, and how long completion can reasonably take. Account for weekends, quiet periods, and batch schedules so low volume is not automatically a failure. Decide what evidence confirms the business outcome: a reconciled record, an assigned job, or a delivered update.
Watch four different signals
Track failures, unexpected volume, stale outputs, and unresolved exceptions. These signals answer different questions. Error counts reveal visible faults, while freshness checks detect workflows that stopped running at all. Sample destination records to catch mapping changes that still return success. A green workflow log is one signal, not the entire monitoring system.
Make alerts lead to action
Every alert needs a responsible owner, an explanation of the business impact, and a safe first investigation step. Group repeated alerts so the same failure does not create a wall of notifications. Test the escalation path when the usual owner is unavailable. Review ignored alerts: they may need better thresholds, clearer ownership, or retirement.
WORKED EXAMPLE / ILLUSTRATIVE
A fictional nightly job import
The import reports no errors, but the destination's last completed job is two days old. A freshness alert identifies the missing outcome even when there is no failed run to inspect.
| Signal | Observation | Response |
|---|---|---|
| Execution errors | None | Does not prove completion |
| Last successful output | Two days old | Investigate source and schedule |
| Exception queue | Six unassigned items | Assign review ownership |
MAKE IT USEFUL
Automation monitoring contract
Define what a person should do when each signal changes.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Detect a workflow that never starts.
- Inspect a sample of successful outputs.
- Assign exceptions, not just alerts.
- Test backup ownership.
Thresholds should reflect your workflow and impact. Copying another business's alert numbers can create noise or hide a problem.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.