GPT-4o does return empty responses

Dietrich Wettschereck 0 Reputation points

After upgrading from GTP-4 to GPT-4o my chat bot does often not respond with any content to user input.

I am using a dedicated assistant and the streaming interface. After submitting a new messages to the thread and starting the run, the chat completion does often return just an empty run.

Here is an example conversation:

User: "Show me a list of my products and let me select an item from it"

Assistant: ... shows some list and asks the use to select from it by selecting the list index

User: "1"

Assistant: no response whatsover

User: "1."

Assistant: no response

User: "hello?"

Assistant: ... correct response that was expected in the first place

Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
2,607 questions
{count} votes

1 answer

Sort by: Most helpful
  1. santoshkc 6,870 Reputation points Microsoft Vendor

    Hi @Dietrich Wettschereck,

    Thank you for providing more information about your chatbot implementation. It's good to know that you are using "swedencentral," which is among the supported regions for GPT-4o.
    One possible reason for your issue is that the model is not trained on enough data to handle all possible user inputs.

    Another possibility is that there may be an issue with the way the model is being used in your chat bot. It's possible that the streaming interface or the way the messages are being submitted to the thread may be causing the issue.

    Since you mentioned that the OpenAI API works as expected with more or less identical code, it's possible that the issue is specific to the way the GPT-4o model is being used in your chat bot.

    I would recommend checking the OpenAI API documentation for any specific requirements or limitations for using the GPT-4o model. You can also try testing the model with different user inputs to see if the issue persists. If the issue continues, you may want to consider reaching out to Azure support for further assistance.

    0 comments No comments