- family
- propagation
- severity
- systemic
- triggerError
- A failure originates at one workflow node (via a natural-language interaction, tool invocation, or control-logic error) but produces no observable symptom at the point of origin.
- mechanism
- The erroneous output flows downstream as apparently valid data; subsequent nodes consume it and build further actions on it, so the visible failure symptom materializes at a node far removed from the actual root cause, entangling attribution.
- blastRadius
- In 32% of observed failures the root-cause node differs from the symptom node, with propagation distances exceeding 40% of total workflow length in over 10% of cases; LLM/Agent and Logic/Control nodes are disproportionately prone to non-local manifestation.
- mast
[Cat 1][Cat 2][Cat 3]
- detection
- Causal-attribution tracing that links observable failure symptoms back through the dependency graph to their origin node; runtime provenance logs on each inter-node message.
- mitigation
- Lightweight validation gates at each stage boundary so bad output is caught at the producer node before entering the shared message channel; anomaly detection on inter-node payloads rather than only on final output.
