Checkpoint

It creates a savepoint in the flow, enabling the conversation to resume from that point based on user input or system signals.

Setting up checkpoints:

1. Place checkpoint node at key conversation points

2. Configure "Wait for user input" if interaction is needed

3. Connect both user input and signal paths if required

4. Create paths for different continuation scenarios

5. Link to appropriate next steps in the flow

Example: As shown in the screenshot, checkpoints are used after intent recognition to maintain conversation state:

Example of using Checkpoints

Intent matcher identifies topic:
- Pricing questions
- Troubleshooting needs
- Upgrade requests

Each path has Checkpoint:
- Wait for user input enabled
- Handle both user responses and signals
- Continue with appropriate LLM responses
- Maintain context through the interaction

Common use cases:

• Maintain conversation state during multi-step processes

• Handle interruptions gracefully

• Create conversation branches

• Manage form-filling and data collection sequences

Important considerations:

• Consider both user inputs and system signals

• Consider using "Go to flow" for more complex paths

• Test checkpoint returns thoroughly

• Plan checkpoint connections carefully