-
Notifications
You must be signed in to change notification settings - Fork 23
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
Facing "You have exceeded a secondary rate limit" when trying to clean deployments up #41
Comments
Can you suggest a solution for this problem |
PR's are welcome. I currently don't have time to add rate limiting but will look to in the future. |
If the developer would like, I wrote some edits to the script to add delays. Before I was hitting the limit every 100 actions, I just deleted 640 deployments in a single run. Then I just added a new var with:
token: ${{ secrets.GITHUB_TOKEN }}
environment: test-remove-deployment-ref-only
onlyRemoveDeployments: true
delay: "500" Timestamped to test
Of course 500ms is quite long, but it can be set way lower. Just wanted to ensure it was properly firing. Also created a new test to create 10 deployments for the env and ensure they are deleted. |
I have like 460 deployments and that is probably the reason I'm getting
"Error: You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID ..."
I think it is a good idea to add an option for user to:
Because currently it is impossible to use this action in case you have a large number of deployments (which is actually one of the use cases).
The text was updated successfully, but these errors were encountered: