Skip to main content

ARC-10: Dead Letter Queue

Summary​

ARC-10 focuses on recoverability for Make.com scenarios and n8n workflows. FlowBeacon uses this policy to highlight automations that may lose failed work instead of capturing it for review, replay, or controlled remediation.

Severity: High · Category: Architecture · Platforms: Make.com, n8n

What FlowBeacon Reviews​

  • Whether failed automation activity appears to be preserved for follow-up.
  • Whether teams have a practical path to investigate and recover from failed runs.
  • Whether recoverability is strong enough for important business processes.

Why This Matters​

  • A failed run should become a recoverable event, not silent data loss.
  • Recovery paths reduce business impact when external systems or inputs fail.
  • Preserving failures supports better troubleshooting and stronger operational discipline.

If This Policy Is Flagged​

  1. Define where failed work should be captured for investigation and retry.
  2. Make sure the capture path is reviewed by a responsible team or owner.
  3. Add a recovery process so important failures can be replayed or resolved safely.
  4. Re-run the evaluation after failed work is no longer at risk of being dropped.

Why Users Care​

  • Users avoid losing important business events when an automation hits a failure.
  • Support teams gain a cleaner path to diagnose and recover from incidents.
  • Consultants can design automations that are safer for production use from day one.