🔧 fix: Correct Endpoint Switching on Error Reception

[danny-avila]

🔧 fix: Correct Endpoint Switching on Error Reception

Summary

This pull request addresses an issue where the application was not properly switching endpoints and resetting the conversation if the first message received was an error. This fix ensures that the application updates the conversation state correctly with initial errors, resetting the conversation to maintain a smooth user experience. No dependencies are required for this change.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

To ensure the fix works as expected, the following test process was conducted:

1. Simulated an error response as the first message from the server.
2. Verified that the application detects the error and switches to the alternate endpoint.
3. Confirmed that the conversation is reset after the switch to avoid any inconsistencies.

To reproduce these tests:

• Configure the server to return an error response as the first message.
• Run the application and observe the behavior to ensure that the endpoint switch and conversation reset occur without any user intervention.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes