I am using assistant api from the openai, it is working perfectly fine but sometimes it doesn’t respond me with anything and also doesn’t throw any error, so basically a user gets stucks and waits for a response which will never going to come back from the api.
This peculiar behavior occurs approximately 1 in 10 times, and I’m looking for insights or potential solutions from the community.
When using a remote API of any kind it is best practice to issue the API call and then begin a timer to check if a reply has been received in an acceptable period of time, if not, the user should be informed. You may wish to show a progress bar or some other visual indicator of “progress” to prevent users thinking the application has crashed.
That error rate is higher than I’ve seen, so I wonder if you are expecting to receive a response immediately instead of polling multiple times with a delay.
Can you share how you are calling the following command in your code, and what you are doing with the “status” value to help you debug?
run = client.beta.threads.runs.retrieve(thread_id=my_thread_id, run_id=my_run_id)
Hi @shakirsnakescript , I have the same problem, in my last 13 calls it failed 6 times (four of them the same day, consecutively). I also noticed I am being charged for the prompt and instructions on these failed runs without completions. I tried to contact support but didn’t get far. Will reply back to the thread if I manage to get some insights into the problem.
I’ve encountered an issue while attempting to connect to my Assistant using the API.
Despite following the documentation for endpoints and ensuring my API key and Assistant ID are correct, I receive an ‘Invalid URL’ error when trying to access chat completions. Could you please provide guidance on the correct endpoint to use or any additional steps I might be missing to establish a successful connection?
I’ve verified the Assistant ID is correct.
From my website, this error popped up: OpenAI Error: Invalid URL (POST /v1/assistants/{assistant_id number}/messages)
That URL was me following ChatGPT’s advice to test my Assistant connection via Postman due to persistent ‘undefined’ response/message/error. This happens whenever I prompt anything for my Assistant to process in my website’s chat interface.
After a thorough review of documentation and insights from ChatGPT and Github Copilot, the challenge persisted until I tried Postman. However, encountering an error in Postman still led to uncertainties about; whether the problem was with the endpoint for Postman or the Assistant’s actual accessibility through Postman and my website.
I’m seeking your help to review my simple plugin’s main code to confirm it’s set up for proper communication and response retrieval from the OpenAI Assistant.
For the second day, I’ve been observing a similar issue where the task returns a status of in_progress for a few seconds, and then responses cease without returning any errors. The result may come back after a delay of 10 minutes, or sometimes not at all. Previously, everything was working stably; the problem seems to be on OpenAI’s side.
Please review the link I gave in the previous post which contains the curl commands required to use the assistants API, asking ChatGPT to create code about a system that it has no knowledge of will result in errors like this, unfortunately there are still aspects of code creation that require human input, you could try pasting the contents of that assistants guide page into ChatGPT as context and then asking for the correct code.
I’ve tried that, can you provide some URL with the correct endpoints for me to check on Postman if my assistant can be connected? I’ve tried both of the following and they failed;
I’m also experiencing same Issue. Sometimes assistant takes “completed” status but doesn’t return a response. I also noticed I’ve been charged for the message but I never received it.
I found a video on YouTube called “# OpenAI Assistants API + Curl How to get started? EASY way to create Assistants (Full Tutorial)” by Mervin Praison.
This video has been very helpful to me to connect the Assistant through CURL.
Hi all
I’m using the assistant APIs with the Bubble API Connector Plugin and its is happening 2/10 times to me. Can we re-call the API to generate the response somehow?
In my case, it generates a response and then gets stuck midway. I wonder how can I really detect that ?
If I would get nothing at all, then i can wait for a defined timeframe and request it again, but in my case it says something like ‘please hold on while i look up your item’ and then nothing happens. (i’m using file_search tool)
Did anyone else experience the same issue ? I’m still stuck and looking for a solution.