AutomationThe job that fails without a sound
What it looks like nowA nightly backup or reminder stops working and nobody notices for a month.
Job failsA month later, someone notices
What changesYou get a message the moment anything that runs on its own fails.
Job failsMessage arrives
Arrives asTextEmailTeamsSlack
See it working: Automation monitoring dashboard
Three ways to fix it
Start small and stop there, or go further. Each one works on its own.
Anything that runs on a timer counts, reports included. If that is yours, see The monthly report.
Which fix suits you?
Does your team already use Teams, Slack or a similar chat?
How many people touch this job?
Answer two questions and the route that suits you lights up.
Suits you bestQuick fix: automate itA message the moment it fails
Good when: You have a handful of things that run on their own.
Every backup, report and reminder checks in when it runs. If one misses, you get a text or an email.
How it knows: if a job does not check in on time, that silence is what sets off the message.
Usually takes1 to 2 weeks
Suits you bestUse what you have: connect itAlerts where you already look
Good when: Your team lives in Teams or Slack.
Failures land in the place you already check, such as Teams, Slack or your phone, with what went wrong.
Example messageThe nightly backup did not run last night. Last good run: Tuesday.
Usually takes1 to 2 weeks
Suits you bestDo it properly: build itOne screen for everything that runs
Good when: Lots of jobs run, and nobody knows them all.
A control screen listing every scheduled job, its last result and what to do when one fails.
Last ranRuns nextHow it went
Usually takes4 to 8 weeks
Timeframes are a rough guide. You get one fixed quote before any work starts. What changes the price?
A job that runs fine stays quiet. You only hear when something needs you.
Support is only ever for a system I built or configured for you. How support works
Your first half hour is free. I reply within 1 business day (Monday to Friday).