Skip to content
Routario Docs

Keeping your automations healthy

Automations finish quietly. A flow that starts failing, an agent whose task lookup errors a third of the time, a job whose runs have slowly gone from clean to “finished, but with errors” — none of that pages anyone. The evidence is sitting right there in your Runs log, but reading it every day is nobody’s job.

The Jobs hygiene reviewer makes it somebody’s job. It’s an agent that reads how your automations have been finishing, on a schedule, notices the patterns worth caring about, and drops a proposal in your Inbox — “this looks like it’s breaking, here’s the fix” — for you to approve or wave off. It never changes anything itself. Silence from it means your automations are healthy; a proposal means something deserves a look.

What it watches

Section titled “What it watches”

Every automation run — a flow or an agent — finishes in one of a few states: it completed cleanly, it completed with errors (it got to the end, but something went wrong along the way), or it failed outright. There’s also a quieter signal: an agent run can finish green and still have hit an error it recovered from on a retry — fine once, worth noticing when it happens run after run, because a bug that self-heals today won’t forever.

On each of its scheduled passes (daily by default), the reviewer reads the recent run outcomes across your automations and looks for patterns, not one-off blips:

  • A specific flow or agent that has failed repeatedly — a rate, not a single flaky run.
  • A tool an agent keeps erroring on, even when it recovers each time.
  • A job whose share of completed-with-errors runs is climbing versus its clean ones.

A single failure isn’t a finding. It’s the trend that earns a mention.

How it tells you — and what it won’t do

Section titled “How it tells you — and what it won’t do”

When the reviewer spots something genuine, it doesn’t fix it. It proposes. A card lands in your Inbox naming what it saw — the affected flow or agent, the rate, the window — and a suggested next step. You Approve, Decline, or ignore it. This is the same propose-and-confirm model every agent uses when it wants to change something: nothing happens until a person says so.

Approve a finding and the reviewer’s one and only write happens — it files a maintenance task describing the pattern and the suggested fix, so the work is captured somewhere you’ll see it. That’s the whole extent of what it can do. It reads run history and it writes a task once you’ve agreed. It never edits a flow, changes a setting, touches your data, or “fixes” anything on its own.

A worked example

Section titled “A worked example”

The reviewer’s morning pass reads the last week of runs and notices your Growth agent’s List Tasks step errored in 6 of its 20 runs — each time it recovered and finished green, so no run looked broken on its own. It proposes:

Jobs hygiene reviewer — needs a decision Growth agent’s List Tasks tool errored in 6 of 20 runs this week (all recovered). File a maintenance task to fix the status filter? Approve · Decline

You approve. A task — “Growth agent: List Tasks errors ~30% of runs — check the status filter” — appears in your tasks with the run details, and you (or whoever owns that agent) picks it up. Nothing about the Growth agent changed; you just found out about a slow leak before it became an outage.

How you get it

Section titled “How you get it”

The Jobs hygiene reviewer is a maintenance job set up by whoever runs your Routario instance, rather than something you install from the jobs catalogue yourself. Once it’s in place it runs on its own schedule and its proposals arrive in the Inbox like any other. If you’d like it watching your workspace, ask your Routario administrator or contact.

Where to go next

Section titled “Where to go next”