Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've had a few customers recently submit support cases who wanted to understand the detailed workings of rate limits.
From my understanding, and reading a few SF KB articles, if you set the rate limit in Braze to be "10,000 messages per minute", Braze does NOT divide 10k by 60 seconds and then send 166 messages each second over the 60 second periods. Braze will send as many messages as possible as quickly as possible, but will NOT send more than 10,000 messages in a 60 second period.
This is due to a number of factors such a Connected Content... and if some calls fail or take longer to retrieve then Braze might not have sent those 166 messages and therefore needs to send more in the following seconds, which would break the "spread out the rate limit over 60 seconds perfectly evenly" rule".
However from working at Braze for 4.5yrs and speaking with customers... Every. Single. Customer. assumes the rate limit does split out the 10,000 messages evenly across the 60 second time period and so uses that calculation to determine their infrastructure capacity.
I felt it important to provide this insight in the docs hence my updates... if you think relevant.
Thanks!
Summary
My PR...
Related PRs, issues, or features (optional)
Feature release date (optional)
Contributor checklist
Submitting for review
If your PR meets the above requirements, select Ready for review, then add a reviewer:
braze-inc/docs-team
as the reviewer.braze-inc/docs-team
instead.Thanks for contributing! We look forward to reading your work.