Control the run
End
Ends the run as Completed when records reach it; steps that have not run are skipped.
Nodes › LogicOpen in Neblex
- Good for
- Finishing early on purpose
- Role
- Works on the records in a flow
- Find it in
- Nodes › Logic
When to use it
- A branch means nothing more needs doing, such as a duplicate order.
- Waiting steps should be skipped once the outcome is known.
- The run should end as Completed, not Failed.
Reach for something else when
Example
When the order already exists, End the run as Completed instead of creating it again.
How it works
- Output
- Its records, unchanged. Steps that have not run yet are skipped, including one that is waiting. A branch that brings no records to End does not end the run.
Add it to a flow
- Open the flow from Build › Workflows.
- Open Nodes and find End under Logic, or search for it. Click it or drag it onto the canvas.
- Drag from the previous step's output handle to its input, then open its settings with ✎ Edit.
- Run the flow and click the step to see the records it received and produced.
More in Control the run
LoopRepeats a group of steps for each record, a set number of times, or while or until a condition holds.Nodes › LogicRun another flowRuns another flow as a reusable sub-flow and continues with its result.Nodes › LogicWaitPauses for a set time before passing records on.Nodes › LogicWait for eventPauses the run until a matching event arrives, then continues with its data.Nodes › LogicSet valueSaves a named value that later steps in the same run can read.Nodes › LogicAssert Data QualityChecks the batch against your rules and stops with precise details when one fails.Nodes › Logic