I’m a tier 5 customer. I do a lot of tts with tts-1-hd. A few weeks ago I switched from “pcm” to “wav” format. I noticed, that sometimes an empty response was sent, so I added a retry which worked fine for 4 weeks or so. Since yesterday or so it does no longer send empty responses but loops forever (it seems). About 50% of my requests time out after 10 Minutes, while the successful ones are processed in a few seconds. If I add enough retries, it works but that’s not a solution. I tried the lower quality tts-1 with same results. Please bring tts-1-hd back to normal. Thanks
There was a major outage that status says is resolved, but we’re still seeing nearly 100% errors in our TTS pipeline
I found that it seems to occur if I run multiple TTS calls from a single runtime in parallel. Adding a sleep in between running each call seems to help. But the API has not returned to the performance we saw before the downtime.
is this only happening today? The API is not working reliably today and hasn’t recovered in my experience even though the outage has been solved purportedly on openAI status
(@ashwath Hope you don’t mind — merged your other post since it’s the same issue.)
Sorry for the issues here, both! We’ve made some improvements over here to address TTS reliability — can you try now?
1 Like
No, I am still seeing the same hanging issue with parallel streams, even when i sleep between processes. This is completely breaking for us, unfortunately.
Same here. I reduced timeout to 2.5 Minutes and it failed again. After 1 retry it succeeded but that would not be a solution for many reasons.
early evidence – but we seem to be back up
I am still experiencing issues, tts-1 still hanging for me.
For me, timeout is gone but now it throws HTTP 502 in maybe 5% of the requests. With a few retries I get my stuff done but would prefer to not having to deal with this kind of errors.
1 Like
In the last 30 Minutes I only had a single timeout and no 502. Looks like they fixed it and it needs some time to roll out. THANK YOU !!!
I’m still getting issues on my parallel TTS pipeline. Usually, 1-3 clips hang or take 5+ minutes to complete. This has been occurring for the past three days and is still happening.
I had only a single problem where tts-1-hd sent an empty response (empty wav file with no sound)