New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leftover deploy pt. 2 - March 1, 2024 #6988
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I was working with a customer who has Talon.One and they said the T1 docs said a 2,500 rate limit is what T1 stipulate. Whereas the Braze docs says 5,000. T1 docs are here: https://docs.talon.one/docs/dev/technology-partners/braze#:~:text=Braze%20supports%20per%2Dminute%20rate%20limiting%20for%20sending%20messages.%20To%20ensure%20that%20it%20matches%20the%20default%20per%2Dsecond%20rate%20limit%20of%20our%20CEP%20endpoints%2C%20in%20your%20Braze%20settings%2C%20set%20Delivery%20Speed%20Rate%2DLimiting%20to%20a%20maximum%20of%202500%20requests%20per%20minute%20or%20lower%2C%20if%20required. I reached our via our Partnerships team and T1 came back and said: "Talon.One can easily handle 300 requests per second (hence 18 000 requests per minute) BUT they need to be evenly distributed (which is the issue as Braze does not distribute evenly) For the moment 2500 requests per minute seems to be the recommended limit to make sure the bursts don't impact the client while the teams are working towards increasing the limits for large clients such as Costa Coffee or Flink"
Update talonone.md
add cloudflare ip ranges
CO-2350 Add catalog permissions.
BD-2872 Troubleshooting push not sending - Android
Update index.md
Update ab_test_projection.md
BD-2875 Add Show archived content
lydia-xie
changed the title
Ad hoc deploy - March 1, 2024
Leftover deploy pt. 2 - March 1, 2024
Mar 1, 2024
rachel-feinberg
approved these changes
Mar 1, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#6970 - Update talonone.md
#6977 - add cloudflare ip ranges
#6978 - CO-2350 Add catalog permissions.
#6972 - Troubleshooting push not sending - Android
#6980 - Update index.md
#6981 - Update ab_test_projection.md
#6983 - Add Show archived content