Return
Type
module.returnbasic/moduleAny
Value
Any
Return (palette name Return, canvas label End, type module.return) finishes a path. Connect the last block of that path into it. There is no outgoing handle.
On the main path, this is what callers receive. Map fields to Start Output schema. Defining that schema is not enough — a completing path must reach Return.
Inside a Lambda body, Return finishes this body (this iteration or task), not the whole workflow. The parent loop or Async task collects that value. The mapped shape must match the parent Callback return shape — or Lambda’s Output schema when you set one.
This block is valid in any scope. Use Break or Continue inside a loop when you want a control signal instead of a collected value.
Configure
Open the cog on the block (dialog header End configuration).
| Setting | Description |
|---|---|
| Output | Bind each property of the resolved output schema (literal or a context path) |
The form follows the schema found upstream:
| Where Return sits | Schema used |
|---|---|
| Main path | Start Output schema |
| Nested callback | Lambda Output schema if you applied one; otherwise the parent Callback return shape |
If nothing upstream defines a schema, the dialog explains that End is not connected through Start or a callback handle.
Each property name must match the schema exactly (total, not Total).
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection from the last block on this path |
There is no Out. Branching paths each need their own Return (or merge into one).
Pipe schema
This block does not pass a value to a later block on the same path. The mapped Output is what the caller (main path) or the parent callback (nested body) receives.