Skip to content

Add retries back on 503s #2244

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

Open
kt474 opened this issue Apr 30, 2025 · 0 comments · May be fixed by #2246
Open

Add retries back on 503s #2244

kt474 opened this issue Apr 30, 2025 · 0 comments · May be fixed by #2246
Assignees
Labels
bug Something isn't working

Comments

@kt474
Copy link
Member

kt474 commented Apr 30, 2025

Retries on 503s were removed as a part of #2099 because we wanted to make sure a proper error message was shown where there was a maintenance outage. This was not the best approach because we still want to keep these retries for other network outages (Cloudflare).

When there is a maintenance outage we can go through the retry logic first and then show the proper error message at the end.

@kt474 kt474 added the bug Something isn't working label Apr 30, 2025
@kt474 kt474 self-assigned this May 1, 2025
@kt474 kt474 linked a pull request May 2, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant