-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
code 503 (availability) #814
Comments
I'm also experiencing the same thing. Please act quickly. |
same |
Yep, seems like runners with node16 are rolling out atm gradually and workflows with old actions started failing. |
We are lucky to have experienced a failure of GitHub, so it's not your fault. |
Should we just wait for them? I have the same with 'actions/checkout@v3' |
Yes, I waited for like 30 minutes, and then it's fine; the error message shows it's an error of the GitHub API. |
They recently released a new version of check-out. I changed my action to checkout@v4 and worked. |
I remain use v3, and did nothing, now it works very smooth. |
Still getting 503 already at "Set up job". |
I get |
Looks like sporadically on GitHub. Currently runs fine again for me. |
Download action repository 'actions/checkout@v2'

Warning: Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/7884fcad6b5d53d10323aee724dc68d8b9096a2e'. Error: Response status code does not indicate success: 503 (Service Unavailable).
Warning: Back off 16.547 seconds before retry.
Warning: Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/7884fcad6b5d53d10323aee724dc68d8b9096a2e'. Error: Response status code does not indicate success: 503 (Service Unavailable).
Warning: Back off 13.553 seconds before retry.
Error: Response status code does not indicate success: 503 (Service Unavailable).
The text was updated successfully, but these errors were encountered: