Troubleshooting Conversation Flows
Common Issues and Solutions
Flow Not Progressing
Symptoms:
Flow stops unexpectedly
No response from virtual being
Seems stuck at a particular node
Common Causes and Solutions:
Wait for User Input enabled unintentionally
Check toggle settings in each node
Verify flow progression logic
Ensure proper node connections
Missing node connections
Verify all nodes are properly connected
Check for disconnected paths
Ensure all conditions have corresponding paths
Conditional logic issues
Verify If/Else conditions
Check signal values
Ensure all cases are handled
Inconsistent Responses
Symptoms:
Unexpected responses
Missing context
Incorrect flow paths
Solutions:
Context issues
Check conversation history preservation
Verify context variables
Review checkpoint placement
LLM configuration
Review system instructions
Check additional context
Verify model selection
Intent matching problems
Refine intent descriptions
Add more trigger examples
Adjust confidence thresholds
Integration Failures
Symptoms:
Webhook errors
External service connection issues
Missing data
Solutions:
Webhook configuration
Verify URLs
Check authentication
Validate request format
Test endpoints independently
Data table configuration
Verify data availability in tables
Verify query conditions in nodes
Check formats and validation criteria
Custom action issues
Validate action names
Check value passing
Verify system integrations
Performance Issues
Symptoms:
Slow responses
Delayed transitions
Timing inconsistencies
Solutions:
Flow optimization
Simplify complex branches
Reduce unnecessary nodes
Optimize LLM usage (use faster LLMs for quesries and better quality LLMs for response generation)
Connection issues
Verify network stability
Check service status
Monitor response times
Debug Techniques
Using Preview Mode
Test flow in real-time
Use web widget preview
Monitor flow progression
Verify node execution
Go to "Conversations" tab and toggle on "Show system messages"
Click on the relevant node execution message to go to that node in the Conversation flows
Check system signals
Monitor signal generation
Verify signal handling
Test conditional logic
Flow Analysis
Visual inspection
Review flow structure
Check node connections
Identify potential loops
Logic validation
Verify conditional paths
Test edge cases
Check default behaviors
Context tracking
Monitor conversation state
Verify checkpoint behavior
Test state restoration
Edge Cases to Consider
Unexpected User Input
Handle empty responses
Manage invalid data
Process unexpected formats
Integration Failures
Provide fallback responses
Handle service outages
Manage partial data
Prevention Strategies
Testing Protocol
Test all paths regularly
Verify edge cases
Validate integrations
Check error handling
Flow Design
Maintain organized layout
Document complex logic
Plan for failure modes
Monitoring
Track common issues
Monitor performance
Log error patterns
Review user feedback
When to Seek Support
Contact technical support when:
Persistent flow issues despite troubleshooting
Unexpected system behavior
Integration problems with external services
Performance issues affecting user experience
Last updated
Was this helpful?