FlowDrop Workflow Specification 1.0-draft

Retry is opt-in, in place, and immediate

There is no backoff and no delay, so a retry is only ever appropriate where the node is idempotent. That is the author's contract, not the runtime's.

The rule

Normative: this is the rule
  1. A node retries only where its configured maximum retry count is greater than zero; the default is zero.
  2. Only a retryable error output retries.
  3. A retry re-executes the node in place and immediately, with no backoff, and the attempt count persists across the run so the maximum bounds the total attempts.
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 · ERR-11 · changed in spec 1.0