Skip to main content
Skips the current branch when a completion marker exists for the resolved key. Lets a flow avoid redoing work that already succeeded once across runs.

​
Configuration

  • Completion key — string, supports {assign_key} interpolation (same syntax as Flow Log). The key is the dedup unit for the whole org — encode any extra scope (system slug, action name, external id) in the string itself.
  • On match
    • Skip branch (default): halt only this path. Parallel branches keep going; inside Flow Each the next iteration runs cleanly. Nothing is recorded as an error.
    • Halt flow: stop the whole run. The reason is surfaced as an error and outer error policies cannot swallow it.
  • Reason (optional) — message attached to the error when Halt flow trips. Supports {assign_key} interpolation. Defaults to an auto-generated message.

​
Tips

  • Pair with a Mark completed node downstream so the marker is written when the work finishes successfully. Use the same completion_key template on both.
  • Leaving the key blank turns the guard into a pass-through — useful while you’re still wiring up the assigns the template depends on.

​
Ports