Error is reproducible for me as well for all models that support image input + file search.
1 Like
Same here，but it was nice yesterday.
2 Likes
I’m having the same issue
2 Likes
Exactly the same issue when processing pictures
2 Likes
Seeing this on my account too. Just for AssistantsAPI via playground and REST API. Seems to be find on the ChatAPI in the playground. Was working fine yesterday.
Unfortunately the error still exists
I’m still encountering this issue. Deleted all of my vector stores and files in storage, still issues with new assistants.
Any official word on this?
For folks that weren’t affected the last time: around a month ago when the EXACT same thing was happening, we received no communication whatsoever, no indication on the status page, and suddenly, well over 24 hours after the issue started, it was resolved without any communication or acknowledgement.
I started experiencing the same issue yesterday as well. Between this, the abhorrent documentation (or lack of it), and the complete radio silence from OAI, I’m pretty angry.
We are noticing the same issue, here it was working perfectly yesterday and suddenly around 6:34AM PST once I’ve tried to run the analysis using image I’ve constantly got the following issue, I’ve already raised this as an issue for OAI hope they fix it ASAP
Same here with my assistant. It was working perfectly fine until this morning!
Another issue: The “Logs” button in Playground Assistant is no longer working since at least 2 weeks!
1 Like
Same here, we have a brand new production SAAS just released, it’s not a fkn good look! No word at all from OpenAI!?!
1 Like
As I’ve said in my previous message I’ve turned to the support at 10:27AM PST with the hope that they will provide some valuable information or might just help me out of this situation…
The complete oposit happened, at 11:30AM PST I’ve got a message from the support, they just technically copied the ChatGPT says ‘Something went wrong.’ | OpenAI Help Center page content over to the Support Chat
[11:30AM PST]
Hello,
Thank you for reaching out to OpenAI support.
We’re sorry to hear you’re experiencing issues with the Assistant API. The ‘server_error: Sorry, something went wrong.’ message typically indicates a problem on our end. Here are a few steps you can take to troubleshoot and potentially resolve the issue:
- Retry the Request: Sometimes, server errors are temporary. Try making the request again after a few minutes.
- Check Network Settings: Ensure that your network settings are not causing the issue. Disable any VPNs or Web Protect features that might be interfering with the connection.
- Review Your Request: Double-check the format and content of your request to ensure it adheres to the API’s requirements. Make sure the JSON object is correctly structured.
- Playground Issues: If the issue persists in the playground, it might be a broader issue. You can try clearing your browser cache or using a different browser to see if that resolves the problem.
- Contact Support: If the problem continues, please provide the following details to our support team for further investigation:
- The Assistant ID (
MY_ASSISTANT_ID)- The exact request payload you are sending
- The timestamp and timezone of your request
- Any additional relevant details or error messages
For more information on handling errors, you can refer to our error codes guide.
If you need further assistance, please let us know, and we’ll be happy to help.
Best,
OpenAI Support
Then 16 minutes later I’ve got the following message
[11:46AM PST]
Hello,
We’ve noticed that we haven’t received a response from you recently, and we’re hopeful that it’s because you’ve found a solution to your issue or it has been resolved to your satisfaction.
If that’s not the case, or if you have any more questions or need additional support, please feel free to reach out. We’re more than happy to assist you further. Your experience and satisfaction are our top priorities.
Best,
OpenAI Support
How should I notice the message within 16minutes and try every “suggestion” they providing?
My Original Message which I’ve turned to the support looks like
I’m using the Assisant API and it’s constantly throwing “server_error: Sorry, something went wrong.” over the HTTP calls and over the playground also
The Assistand Id : MY_ASSISTANT_ID
The Instructions :
THE INSTRUCTIONS THAT THE ASSISTANT USES
I’m passing the following text message object:
THE PAYLOAD THAT WE ARE SENDING
and also images to be analyzed
I went through the exact same despair last time this happened @zoltan.balogh. Absolutely no help from support, generic answers, etc, clearly not acknowledging the real problem.
I think we just have to wait and hope that they fix it, like last time. Very frustrating for those of us with production applications depending on this feature.
1 Like
@kelby Exactly, and at least they could have acknowledging there is a problem and tell us that
Hey just wait till tomorrow we are working on it and we’re already in the knowledge of the issue
Let’s wait till they fix it, hope they could address it ASAP
1 Like
FYI
Everyone who is having this issue, I’ve contacted the support again, this time with success, they started to look into this issue
I’ve looked into the issue you’re having with the API platform displaying a “Something went wrong” error message, but I won’t be able to solve it without some help from a colleague.
I’ve shared your question with our specialist team and asked them to investigate further. They’ll get back to you on this thread with a solution as soon as they can.
I’ll try to support the community with and once they get back to me with a possible solution, or with any update, then I’ll also update here
Happy Engineering till then
6 Likes
The error still exists for me. What about you?
2 Likes
Same for me since yesterday.
What do you guys do for alternative or a any backup in such case?
I use it in an app for image analysis. I have tried the Vision Model and others as alternatives, but that doesn’t help either. The problem seems to be related to an assistant ID. If the models are accessed directly via the API, the error does not occur. But since I rely on the vector database, that is not a solution either.
4 Likes