To ensure efficient and smooth service, it is essential to understand the main modes of failure that can occur in Eddie's flows and the communication between Eddie and ClaudIA. Identifying and mitigating these failures enhances the customer experience and prevents unwanted interruptions.
Timeout and Request Cancellation
Communication between ClaudIA and Eddie needs to be quick and efficient to ensure smooth customer service. However, there is a time limit for executing each request within Eddie. If this time is exceeded, the request is automatically canceled, interrupting the flow and preventing the customer from receiving an adequate response.
How Does Timeout Work?
-
When ClaudIA calls a flow from Eddie, the execution of actions within the flow must occur within a time limit of 45 seconds.
-
This limit exists to ensure that the conversation happens in real time, without noticeable delays for the customer.
-
If a request takes longer than this period, Eddie cannot complete the action, resulting in the cancellation of the operation and no response for ClaudIA.
Main Causes of Timeout and Request Cancellation
APIs with High Response Time
-
When an Eddie flow makes a call to an external API, the response time can be very long, exceeding the allowed limit.
-
Some APIs are not optimized for quick queries and may take time to process and return data.
-
If the API does not respond within 45 seconds, the request will be automatically canceled, harming the user experience.
🔹 How to Avoid:
Use APIs that have a fast response time (ideally less than 2-3 seconds).
Prioritize asynchronous APIs or those with cached responses to avoid delays.
If you need a slow API, consider breaking the request into smaller parts or using intermediate solutions (such as storing temporary data).
Retrieval Failure
-
This can happen due to configuration errors, recent changes in the flow, or failures in data indexing.
-
To mitigate this issue, it is essential to regularly review and test the contents attached to the flow.
Internal Execution Error in Eddie
-
Eddie may experience internal failures that prevent the correct execution of the flow.
-
This can occur due to incorrect configurations, poorly structured blocks, or improper use of logical conditions (IF/ELSE).
-
To minimize this risk, it is recommended to test each flow before publication and review error logs in the Hub if it occurs.
Error in Integration Execution
-
External integrations (such as API calls, Google Sheets) may return error messages or fail completely.
-
When this happens, Eddie may follow an incorrect path or not respond to the customer.
-
To mitigate this issue, configure appropriate error handling, such as:
-
Returning an explanatory message to the customer.
-
Escalating service to a human agent (N2).
-
5. Incorrect Execution Flow
-
In flows that use LLMs (Language Models like GPT) to define the execution route, there may be failures in choosing the next step.
-
This occurs when the model's interpretation leads to an unexpected path or when the conditions within the flow are not well defined.
-
To avoid this type of error:
-
Define clear and well-structured prompts.
-
Configure conditional responses for different scenarios.
-
Test variations of the flow to ensure predictability.
-
Total Failure of Eddie
-
In extreme cases, Eddie may fail completely, preventing the flow from continuing.
-
To prevent the customer from getting stuck in the conversation, there is a safety feature that automatically escalates the conversation to N2.
-
This scalability ensures that, even in a scenario of overall failure, customer service is not interrupted.
