# 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:**

1. Wait for User Input enabled unintentionally
   * Check toggle settings in each node
   * Verify flow progression logic
   * Ensure proper node connections
2. Missing node connections
   * Verify all nodes are properly connected
   * Check for disconnected paths
   * Ensure all conditions have corresponding paths
3. 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:**

1. Context issues
   * Check conversation history preservation
   * Verify context variables
   * Review checkpoint placement
2. LLM configuration
   * Review system instructions
   * Check additional context
   * Verify model selection
3. 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:**

1. Webhook configuration
   * Verify URLs
   * Check authentication
   * Validate request format
   * Test endpoints independently
2. Data table configuration
   * Verify data availability in tables
   * Verify query conditions in nodes
   * Check formats and validation criteria
3. Custom action issues
   * Validate action names
   * Check value passing
   * Verify system integrations

**Performance Issues**

**Symptoms:**

* Slow responses
* Delayed transitions
* Timing inconsistencies

**Solutions:**

1. Flow optimization
   * Simplify complex branches
   * Reduce unnecessary nodes
   * Optimize LLM usage (use faster LLMs for quesries and better quality LLMs for response generation)
2. Connection issues
   * Verify network stability
   * Check service status
   * Monitor response times

#### Debug Techniques

**Using Preview Mode**

1. 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

   <figure><img src="/files/cNgKmgUm3xPRaazYYVWJ" alt="" width="563"><figcaption><p>Verify node execution in Conversations tab</p></figcaption></figure>
2. Check system signals
   * Monitor signal generation
   * Verify signal handling
   * Test conditional logic

**Flow Analysis**

1. Visual inspection
   * Review flow structure
   * Check node connections
   * Identify potential loops
2. Logic validation
   * Verify conditional paths
   * Test edge cases
   * Check default behaviors
3. Context tracking
   * Monitor conversation state
   * Verify checkpoint behavior
   * Test state restoration

#### Edge Cases to Consider

1. **Unexpected User Input**
   * Handle empty responses
   * Manage invalid data
   * Process unexpected formats
2. **Integration Failures**
   * Provide fallback responses
   * Handle service outages
   * Manage partial data

#### Prevention Strategies

1. **Testing Protocol**
   * Test all paths regularly
   * Verify edge cases
   * Validate integrations
   * Check error handling
2. **Flow Design**
   * Maintain organized layout
   * Document complex logic
   * Plan for failure modes
3. **Monitoring**
   * Track common issues
   * Monitor performance
   * Log error patterns
   * Review user feedback

#### When to Seek Support

Contact technical support when:

1. Persistent flow issues despite troubleshooting
2. Unexpected system behavior
3. Integration problems with external services
4. Performance issues affecting user experience


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.virbe.ai/dashboard-management/conversation-flows/troubleshooting-conversation-flows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.