Repository navigation
LLM Call: Better Error Messages #874
Description
Is your feature request related to a problem?
When an error occurs in the OpenAI integration, it returns a 200 status with success: false, while providing null values for reason, error_type, and thread_id. This leads to a loss of context in the conversation, causing subsequent turns to break.
Describe the solution you'd like
- Improve error handling to return meaningful messages and proper status codes.
- Ensure that thread_id is provided even in error scenarios to maintain conversation context.
Original issue
Describe the bug
So it's more of an OpenAI thing- just wanted to flag how it lands on our side.
It's an error but comes as 200 + success: false, with reason, error_type and thread_id all null, only signal is the message string, and going forward in the flow the thread_id = null, it breaks the flow, we use the returned thread_id to continue the conversation, so a null here means the conversation loses its context and the next turns break.
To Reproduce
TBD
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]LLM Call: Better error messaged[/-][+]OpenAI Integration: Improve error handling[/+][-]OpenAI Integration: Improve error handling[/-][+]LLM Call: Better Error Messaged_DO_NOT_MODIFY[/+][-]LLM Call: Better Error Messaged_DO_NOT_MODIFY[/-][+]LLM Call: Better Error Messages_DO_NOT_MODIFY[/+][-]LLM Call: Better Error Messages_DO_NOT_MODIFY[/-][+]LLM Call: Better Error Messages[/+]