#Operation timed out

6 messages · Page 1 of 1 (latest)

vagrant saffron
#

Getting this repeatedly... anyone else? Using gpt-3.5-turbo...

Operation timed out after 60006 milliseconds with 0 bytes received

My timeout is set to 60, I have 5x retries per timeout and it times out on all of them.

toxic summit
vagrant saffron
#

The timeouts are just crazy right now. I've never seen 10 timeouts in a row, and I've been using davinci-003 and gpt-3.5-turbo every single day since release.

Operation timed out after 60013 milliseconds with 0 bytes received

Failed after 10 retries.

vagrant saffron
#

Having to tell customers that it's a problem on OpenAI's end, even though the status page on OpenAI's site claims there is no problem. It's frustrating because I'm asking my customers to believe it's not my fault, when they have no evidence that it's not my fault... this really needs to be addressed by the team!

orchid chasm
#

We've seen this as well. It happens way more often than you would expect. It is hard to create a production worthy product with this behavior. Also the fact that it is "chat", that sort of delay in a conversation is a poor user experience. We regularly see 3-6 seconds per request as well

vagrant saffron
# orchid chasm We've seen this as well. It happens way more often than you would expect. It is ...

This happened in February, and it took 10-15 days for enough people to notice and them to fix the issue. I’m assuming that’s what going to happen again… and I’ll somehow have to convince my customers (again) that it’s OpenAI, not my code.

The worst part is that their status page is seemingly not automatically updated. So while we’re getting constant timeouts, customers see everything is operational.