429 Too Many Requests errors when running the action

[kamzil]

Describe the bug

When running a workflow with this action, we're sometimes getting the following in the logs and the step fails:

Download action repository 'aws-actions/configure-aws-credentials@v4' (SHA:e3dd6a429d7300a6a4c196c26e071d42e0343502)
Warning: Failed to download action 'https://api.github.com/repos/aws-actions/configure-aws-credentials/tarball/e3dd6a429d7300a6a4c196c26e071d42e0343502'. Error: Response status code does not indicate success: 429 (Too Many Requests). 0400:1CE9D3:6E430:9ED09:683429C9
Warning: Back off 22.999 seconds before retry.
Warning: Failed to download action 'https://api.github.com/repos/aws-actions/configure-aws-credentials/tarball/e3dd6a429d7300a6a4c196c26e071d42e0343502'. Error: Response status code does not indicate success: 429 (Too Many Requests). 0400:1CE9D3:6E604:9EFE0:683429E0
Warning: Back off 27.472 seconds before retry.
Error: Response status code does not indicate success: 429 (Too Many Requests).

Is there some rate limiting going on in the API? How can this be avoided?

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

There should be no 429 errors.

Current Behavior

There are sometimes 429 errors caused by some kindof rate limiting to GitHub API when it's trying to download the tarball for this action.

Reproduction Steps

Run a GitHub workflow with this action.

Possible Solution

No response

Additional Information/Context

No response

[lehmanmj]

Hi kamzil, thanks for reaching out. We actually haven't seen this error before.

The action runner/job setup stage is outside of our control, so this rate limiting is from GitHub's side. Maybe this page might have some information that could help?

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.