Handle Zendesk API errors #1008
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
Otherwise 500 error is returned. The Client apps can then handle those appropriately. Ideally calling Zendesk API should be done in a worker that would handle all possible Zendesk API errors with appropriate retry logic (e.g. don’t retry on 409 :conflict). The controller should respond with 202 :accepted status rather than 201 :created. It is not implemented at this time due to change in delivery priorities (and this work being reprioritised).
samsimpson1
approved these changes
Aug 9, 2024
AgaDufrat
changed the title
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.
Otherwise 500 error is returned. The Client apps can then handle those appropriately.
Ideally calling Zendesk API should be done in a worker that would handle all possible Zendesk API errors with appropriate retry logic (e.g. don’t retry on 409 :conflict). The controller should respond with 202 :accepted status rather than 201 :created.
It is not implemented at this time due to change in delivery priorities (and this work being reprioritised).
alphagov/support#1422
Follow these steps if you are doing a Rails upgrade.