How do I catch an automation that runs green but does nothing?
An error workflow catches errors. It does not catch the run that finished green and sent nothing, or the one that quietly stopped matching after an API changed shape.
For an agency that hands workflows to clients, that is usually how a problem gets found. The client notices, weeks later.
We are setting up outside checks that look for the result, not the run. It is not a product yet. We are running it by hand, free, for a first small group of agencies.
What we would set up
- For 3 of your client workflows, a written definition of a real result (a reply sent or a row written) and the time it should land by. We agree these with you, because you know what the client actually depends on.
- An alert to you when the run is green but the result never showed up.
- A check on the shape of the output, so an empty or half-filled result counts as a failure.
- A weekly health report with your name on it that you can forward to the client.
What people are saying
Posts we read on October 7, 2026. Upvotes as of that day.
“Empty-because-broken and empty-because-genuinely-empty are the same thing from the outside”
“Found a bug in my production workflow that never once threw an error.”
“Silent schema drift is worse than an outright crash.”
Get early access
Leave your email and we will write to you, by hand, when the first group starts. Tell us what you are running if you want. We read every note.
Who is behind this
Continuum is Matt Turley's studio. We build and look after software for small businesses and founders, and we run our own business on AI agents, which is where these ideas come from. Questions: hello@uxcontinuum.com. Other things we are testing.