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.