Appearance
Stop execution
Stops the processing of the current request: after a record reaches this component, no further component is called for any record that shares the same metadata instance. The flow itself keeps running.
Pins
| Pin | Kind | Types | Description |
|---|---|---|---|
| Input | input | any | Arrival of a record stops its request. |
Configuration
None besides the common settings.
Behaviour
- Sets the
StopExecutionflag on the record's metadata. From then on every attempt to call a next component with this metadata is skipped silently (no error). - Components that are already executing finish their current work; only their further
Nextcalls are skipped. This includes components upstream: for example a loop (Range, ForEach) or a branch that continues after this component returns will not call anything more for that request. - Other requests (with their own metadata, e.g. a new HTTP request or a new Timer tick) are not affected.
Notes
- Typical use: after a filter or an If, end a request early without raising an error.
- Because metadata is shared along the request, stopping in one parallel branch also stops the other branches of the same request.
- For an HTTP listener, make sure a response has been sent before stopping, otherwise the client waits for a timeout.
- To end a request with an error instead, use the Error component.
Example
Http listener → If → (false) → Stop execution