Automation troubleshooting
An automation quietly stopped?
The daily report never arrived. An import is days behind. Invoices stopped appearing. I trace the background process and the work it should have completed.
Did it never run—or stop halfway?
Those situations need different fixes. A job can start on schedule and still produce incomplete output. I compare its last successful result with what should have happened since.
- Nothing ran at the expected time
- The process ran, but its output is missing
- Some records completed and others are stuck
Restarting is not the same as catching up
A manual rerun might send emails twice, duplicate invoices or repeat an export. I check what already completed, then work out which missed tasks can be rerun safely and how future failures should be noticed.
Scheduled-job and background-worker checks
- Cron schedules, service status and execution history
- Credentials, permissions and runtime or API changes
- Queue backlog, locks, retry behavior and partially processed records
- Input files, saved output and duplicate-prevention checks before a backfill
What if the automation depends on an unavailable service?
I can check whether the local job is healthy and what work is waiting. Recovery may need to wait for the other service; the backlog still needs a deliberate retry plan.
What should have happened automatically?
Tell me what is missing and when you last saw it work.