The workflow reliability checklist: 12 things every automation needs before it goes live

Most automation failures are not dramatic. A connected app changes a field name, a token expires, a rate limit trips, and the workflow quietly stops. Nobody notices until a customer does. The fix is not cleverness; it is a checklist applied before launch and reviewed monthly. This is ours.

Design

• Named and described. Every workflow has a name that says what it does, a description of the trigger and the outcome, and an owner.
• Idempotent writes. Running twice never creates duplicates. Every create step checks for an existing record first.
• Explicit scope. The workflow (or agent) can only touch the records and tools it needs, with the least privilege that works.
• A human where it matters. Anything irreversible, expensive or customer-facing has an approval step or a confirmation.

Failure

• Retries with backoff. Transient errors — timeouts, rate limits, a brief outage — retry automatically and stop after a limit.
• An error route. Failed items are held with their data for replay, not dropped.
• Alerts to a person. Repeated failures notify a named person on Slack or email, with a link to the failed run.
• A pause switch. One control stops the workflow without deleting it.

Visibility

• A run log. What came in, what was decided, what went out — for every run, kept for long enough to investigate.
• Cost tracking. Platform operations and model tokens per workflow, with a monthly budget alert.
• A monthly review. Someone reads the error log and the operations count, and retires flows nobody uses.
• Documentation and handover. A one-page map of the workflow, its owners, its secrets (where they live, not what they are) and how to change it.

How to use this

Print the twelve lines and walk through your most important automation. Most flows fail at least four of them, usually retries, the error route, idempotency and the monthly review. Fixing those four removes most of the silent failures. If you would rather we did the walk-through, that is what the free workflow audit is for — and every workflow we build includes all twelve, because that is the job.