FlowDrop Workflow Specification 1.0-draft

An edge leaving a terminal node warns

A terminal node ends the run, so nothing downstream of it will execute. The edge is legal (the author may be mid-edit), but it is almost certainly not what they meant.

The rule

Normative: this is the rule
  1. Every edge whose source node is a terminal node yields one non-blocking warning at edge.{index}, naming the terminal source and the target it leads to.
  2. A terminal node with several outgoing edges therefore produces one warning per edge, and the workflow stays valid.
  3. Only sources are inspected, so a workflow with no edges looks nothing up, and the target's existence is not checked here: an edge from a terminal node to a deleted node produces both this warning and R8's missing-target error.
  4. An edge whose source is itself dangling produces no warning; R8 owns that.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · W-T · changed in spec 1.0