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

# BR-7 — A node whose triggers are all unsatisfied is skipped, not executed

*RT-BR (Part II) · level: core · profiles: runtime · added in 1.0*

This is the line the whole branching design rests on: an untaken branch does not merely fail to fire, it terminates cleanly, visibly, and without failing the run.

## The rule

> **Normative.** This is the rule.
>
> 1. A node with at least one incoming trigger edge and no satisfied trigger is skipped and must not be executed.
>
> 2. The skip is announced with the machine-readable reason `branch_not_active`, on the node-level skip event, on the real-time status update, and on the run's snapshot; the node's identifier also appears among the run's skipped nodes in the response metadata and is counted there.
>
> 3. A node with no incoming trigger edge always executes, whatever its data sources did.
>
> 4. At the end of a run, every node still unexecuted is collected as skipped the same way, whether or not it had already been promoted to ready.

## Related rules

- Names: BR-1, BR-6
- Referenced by: BR-6

---

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.