Skip to content

Commit 3a65d72

Browse files
How do I avoid hitting the Max Channel Message Rate Limit by sharding messages across channels?
1 parent 176ab35 commit 3a65d72

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

src/pages/docs/platform/errors/codes.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -449,6 +449,12 @@ This error occurs when a [limit](/docs/platform/pricing/limits) on your account
449449

450450
An example of this error is when a client exceeds the maximum allowed message rate on a channel.
451451

452+
**Resolution:** To avoid hitting the channel message rate limit, you can:
453+
454+
* Distribute your message load across several channels instead of publishing all messages to a single channel. This allows you to stay within the per-channel limit while maintaining higher overall throughput.
455+
* Configure [server-side batching](/docs/messages/batch#server-side) to group multiple messages into single batches, which reduces the effective message rate and can help avoid rate limits while also reducing costs.
456+
* Contact [[email protected]](mailto:[email protected]) if you need a higher per-channel rate limit than the standard 50 messages per second.
457+
452458
In the following example, the metric `channel.maxRate` represents the maximum rate of messages allowed to be published on a channel per second. The permitted rate is 5000 messages per second, but the client is attempting to publish 5015 messages per second, triggering the limit.
453459

454460
<Code>

0 commit comments

Comments
 (0)