You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When an OpenAI Assistant has access to URLs and turns them into URLs in the chat, either the app or the assistant is removing the link and then turning it plain text. The stream then seems to stop, but data keeps coming intermittently. Every time a url is generated, a new entry is generated as-if it was a new chat response.
To be clear, I can see the app creating the url, then it backs up and drops them.
To Reproduce
Steps to reproduce the behavior:
Tools response data that the OpenAI Assistant contains a URL.
Expected behavior
I expect a single response showing the data and the urls. In turn, I get n-many responses from the bot. The first response has the first data point, the second has the first and second data point, the third has the first, second, and third data point, and so on.
Screenshots
Desktop (please complete the following information):
OS: Windows
Browser: Edge & Chrome
The text was updated successfully, but these errors were encountered:
Describe the bug
When an OpenAI Assistant has access to URLs and turns them into URLs in the chat, either the app or the assistant is removing the link and then turning it plain text. The stream then seems to stop, but data keeps coming intermittently. Every time a url is generated, a new entry is generated as-if it was a new chat response.
To be clear, I can see the app creating the url, then it backs up and drops them.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect a single response showing the data and the urls. In turn, I get n-many responses from the bot. The first response has the first data point, the second has the first and second data point, the third has the first, second, and third data point, and so on.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: