-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
best way to handle ServerError and ServerUnavailable Exception #45
Comments
Is the |
@jeromegamez I ended up using
I have some weird issue with This brings me to the next question: how to try and catch for all |
You can catch the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I usually have a queued job to process sending a push notification. When the job gets a
ServerError
orServerUnavailable
Exception, it will retry immediately until it runs out of the number of tries.Ideally, if the job gets the
ServerError
orServerUnavailable
. It should wait for 30s before trying again. I am not sure how to do this? Any suggestions?The text was updated successfully, but these errors were encountered: