Skip to content

What's a real error vs an expected 'miss' result?

Not every deviation is an error. Customer has no email = exception, not failure. API down = transient error. Auth failure = critical error. The distinction decides if your flow logs, retries, or pings a human.

Try this first

  1. 1Define 3 categories clearly: 'expected miss' (data choice, no action), 'transient' (retry fixes), 'critical' (human needed).
  2. 2Handle expected miss with a continue path, not an error route. Log for traceability, no alert.
  3. 3Handle transient with retry plus exponential backoff. Alert only after N consecutive failures, not the first.
  4. 4Handle critical immediately with notification to the owner plus dead-letter record. Don't wait for a scheduled review.
  5. 5Document per flow where each category applies. Otherwise your error channel clogs with things needing no action.

When to bring us in

Got many false-positive alerts from your flows, usually this categorisation is the cause. A few hours' audit fixes it.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.