Continue Processing
Passes the current event from a Handler into the Conversational Flows layer.
The Continue Processing node is the "done" signal at the end of a Handler. When execution reaches this node, the Handler finishes and control is passed to the Conversational Flows layer, which then processes the event normally.
Available in: Handlers only.
When to Use
Every execution path in every Handler must end with either Continue Processing or Abandon Processing. If a path has no exit node, the event is silently dropped.
Use Continue Processing whenever the Handler has finished its pre-processing work and the event should proceed to Conversational Flows as normal.
Behavior
- Execution of the current Handler stops
- The event (user message, signal) is forwarded to the active Conversational Flow
- The Conversational Flow then handles the event as it normally would
Contrast with Abandon Processing
| Continue Processing | Abandon Processing | |
|---|---|---|
| Passes event to flows? | ✅ Yes | ❌ No |
| Response generated? | ✅ Yes (by flows) | ❌ No – event is dropped |
| Use when | Handler work is done, proceed normally | Input should be filtered or ignored |