---
id: ERR-10
family: RT-ERR
level: extended
profiles: [runtime]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/rt-err/err-10
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# ERR-10 — A routed failure activates error edges only, and only when it is current

*RT-ERR (Part II) · level: extended · profiles: runtime · added in 1.0*

Two independent staleness rules guard the handler, because a loop can both re-run a node and route a failure from an earlier round.

## The rule

> **Normative.** This is the rule.
>
> 1. A node whose failure was routed satisfies only its error edges.
>
> 2. Error edges are evaluated before trigger and data edges and combine with OR semantics: one satisfied error edge activates the handler.
>
> 3. Success-path successors are never made ready by a routed failure.
>
> 4. A routed failure does not activate its handler when a newer unit of work exists for the same node, nor when it was routed in an earlier round than the round the handler has already handled.

## Related rules

- Names: ERR-7, SG-19
- Referenced by: ERR-7

---

Rule identifiers are permanent and are never renumbered. This specification carries
no implementation status: each implementation publishes its own standing against
these rules. Licensed CC BY 4.0.