Several TTS Synthesis errors: "ResourceExhausted"/1013 and "NotFound"/1007

Uii Dev Team 1

Recently we've been seeing increased error output when performing speech synthesis using the Node.JS SDK. This seems to happen after a number of transactions (30-60), but not every time. The errors appear mixed, with the first starting to appear before the second error starts appearing. The same content has been run through synthesis without errors before. We're on a Standard (S0) subscription, so the higher rate limits should apply. Our resource region is set to eastus.

Status(StatusCode="NotFound", Detail="service does not exist: service endpoint xds:///bg-bg-combogro websocket error code: 1007

Status(StatusCode="ResourceExhausted", Detail="no tokens available for passthrough") websocket error code: 1013

romungi-MSFT 48,406 Reputation points Microsoft Employee

2022-10-21T09:21:37.1+00:00

@Uii Dev Team Thanks for reporting. I am checking internally for any known issues with the service.
Uii Dev Team 1 Reputation point

2022-10-26T23:23:15.177+00:00

Any word on what might be happening or what some of these error messages entail?

We've also seen errors pop up since posting this:

Status(StatusCode="ResourceExhausted", Detail="No free synthesizer") websocket error code: 1013

We're wondering if this is caused by rate limits or it's something on Microsoft's side. The errors have been fairly inconsistent. Recently we started tracking WordBoundary events and wondered if it's somehow counting against the rate limit.

Share via

Several TTS Synthesis errors: "ResourceExhausted"/1013 and "NotFound"/1007

Your answer