Azure Communication Services Chat Service Degradation and Slow Response Times

Andreas Nyhrén 10

The ACS Chat Service endpoints (create identity, get token, create chat thread, etc.) have historically not been fast. Previously, response times were in the range of 200-600 ms, but recently response times have increased to over 30 seconds, and in some cases, up to over a minute.

The system is using the .NET Chat SDK with Azure Functions.

SnehaAgrawal-MSFT 21,926 Reputation points

2024-12-11T10:08:55.9566667+00:00
@Andreas Nyhrén Thanks for reaching here! If i have understood right you are facing slow response time- Could you please confirm service limits for Chat-

The maximum number of participants allowed in a chat thread is 250.

The maximum message size allowed is approximately 28 KB.

For chat threads with more than 20 participants, read receipts and typing indicator features aren't supported.

For Teams Interop scenarios, it's the number of Azure Communication Services users, not Teams users, that must be below 20 for the typing indicator feature to be supported.

When creating a chat thread, you can set the retention policy between 30 and 90 days.

Moreover, in Teams Interop scenarios, there are the following limitations:

The Teams user's display name in typing indicator event is blank.

Read receipt isn't supported.

Certain identities are not supported (i.e. Bot users, Skype users, non-enterprise users, etc.)

See- https://learn.microsoft.com/en-us/azure/communication-services/concepts/service-limits#size-limits-for-chat
Andreas Nyhrén 10 Reputation points

2024-12-11T10:34:43.0133333+00:00

yes (with the exception of retention policy which can only be set using the 1.3.0-preview release of the SDK, we're on latest stable which is 1.3.1 which still does not allow retention policy to be set, which we find a bit strange - care to explain? guessing that feat did not make stable release and will be added later?), we're aware of the service limits and have no indications (429-responses) of us hitting any limits in this context.

we've also described our issue on github: https://github.com/Azure/azure-sdk-for-net/issues/47463 most notably we have quite a few timeouts and in addition a lot of really slow response times:

cases where GetAccessToken (POST /identities/<ACS UserId>/:issueAccessToken) completely times out (InvocationIds):
b5b1845e-fa3c-4000-8632-315256c01552
3206e6ee-1623-482c-8f8c-609fafc80d80
3a121576-8b85-4a35-a3c9-598e95e67f9e

cases where GetAccessToken (POST /identities/<ACS UserId>/:issueAccessToken) has very long response times
InvocationId e292e400-e496-4d71-9fbc-8a97d2405960, ClientRequestId 3a4472f4-96db-4c3a-87d6-c45192ab9562 37,2 secs
InvocationId 6140e077-5f38-497e-8abd-a7cf7d101b5c, ClientRequestId 56634e3c-4d46-4c10-9bae-356ef7423627 24,7 secs
InvocationId 04ecde28-b625-4ea5-bb6d-2e8afe9ebb06, ClientRequestId 6fca2aed-07c9-4d97-b95a-51ee28822547, 12,6 secs
Andreas Nyhrén 10 Reputation points

2024-12-13T13:12:05.6733333+00:00

Some more slow invocations or with timeouts:
bf7f49d6-6350-4999-baf7-37120a39bb0c ClientRequestIds: f988cbc0-6b78-4761-8ef7-a3eed666184d (timeout, 4 retries)
cb830c6f-c101-4a08-8f4c-07051fbd0e3f ClientRequestIds: 02f4db24-9a6b-45b2-a2c5-8df56e7c7399 (1.5 mins)
345b39ba-a6b8-46da-bf10-4d134007fb0b ClientRequestIds: 2724f05f-0699-42fe-9b12-3de880c2c6e2 (one timeout 100 sec, 23.2 secs 2nd retry)
SnehaAgrawal-MSFT 21,926 Reputation points

2024-12-16T04:07:25.79+00:00

@Andreas Nyhrén Thanks for response! Reached you privately.

Share via

Azure Communication Services Chat Service Degradation and Slow Response Times

Your answer