Skip to content

Commit de732f2

Browse files
Merge pull request #229029 from kperla97/patch-6
Update service-limits.md
2 parents e17fa94 + 522f691 commit de732f2

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/communication-services/concepts/service-limits.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: shahen
77
services: azure-communication-services
88

99
ms.author: chpalm
10-
ms.date: 11/01/2021
10+
ms.date: 02/28/2023
1111
ms.topic: how-to
1212
ms.service: azure-communication-services
1313
ms.subservice: data
@@ -17,7 +17,7 @@ ms.subservice: data
1717
This document explains the limitations of Azure Communication Services APIs and possible resolutions.
1818

1919
## Throttling patterns and architecture
20-
When you hit service limitations, you'll generally receive an HTTP status code 429 (Too many requests). In general, the following are best practices for handling throttling:
20+
When you hit service limitations, you will receive an HTTP status code 429 (Too many requests). In general, the following are best practices for handling throttling:
2121

2222
- Reduce the number of operations per request.
2323
- Reduce the frequency of calls.
@@ -124,6 +124,9 @@ This sandbox setup is to help developers start building the application. You can
124124
|Send typing indicator|User and chat thread|5|15|
125125
|Send typing indicator|Chat thread|10|30|
126126

127+
### Chat storage
128+
Chat messages are stored for 90 days. Submit [a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md) if you require storage for longer time period. If the time period is less than 90 days for chat messages, use the delete chat thread APIs.
129+
127130
## Voice and video calling
128131

129132
### Call maximum limitations
@@ -140,7 +143,7 @@ The Communication Services Calling SDK supports the following streaming configur
140143
| **Maximum # of outgoing local streams that you can send simultaneously** | one video or one screen sharing | one video + one screen sharing |
141144
| **Maximum # of incoming remote streams that you can render simultaneously** | four videos + one screen sharing | six videos + one screen sharing |
142145

143-
While the Calling SDK won't enforce these limits, your users may experience performance degradation if they're exceeded.
146+
While the Calling SDK will not enforce these limits, your users may experience performance degradation if they're exceeded.
144147

145148
### Calling SDK timeouts
146149

0 commit comments

Comments
 (0)