-
Notifications
You must be signed in to change notification settings - Fork 1
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
BCDA-7867: Add 429 recommendations #193
Conversation
Suggest adding something along the lines of bcda-static-site/_includes/build/requesting_data_runouts.html Lines 64 to 66 in 01f86bb
|
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.
Requesting review from Jennifer via slack
|
Thanks for adding this Alex! I will approve; do we also have approval from someone on the content team? |
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.
Sharing Jennifer's review and content edits
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.
🎫 Ticket
https://jira.cms.gov/browse/BCDA-7867
🛠 Changes
Added best practices section to "Building Your Application" page, with first best practice being handling 429 status codes.
ℹ️ Context for reviewers
BCDA has two 429 mechanisms, neither of which currently shows recommendations on how to avoid / handle them. By clearly outlining how we recommend clients handle them, we can improve the quality of the BCDA experience and decrease the number of posts that require triaging in the google group.
✅ Acceptance Validation
🔒 Security Implications
If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.