-
-
Notifications
You must be signed in to change notification settings - Fork 508
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
Exception: Query 'repo_commit_list' failed to run by returning code of 403: 'message': 'You have exceeded a secondary rate limit. Please wait a few minutes before you try again.' #431
Comments
@SemenMartynov it looks like your workflow has been failing for more than month for various reasons. However, the most recent executions are related to the error you're pointing out. Could you confirm if your GitHub token is unique and not being used elsewhere? Could you regenerate the token and keep it unique to your repository for this workflow? |
I have same issue
What's the problem ? @anmol098 |
The key was definitely unique and was not used anywhere else. But I re-generated it anyway, and in a strange way it turned out to be a solution. @ssoad please try to do the same. |
Thanks for confirming @SemenMartynov! I'll keep this open for @ssoad also to confirm. |
@SemenMartynov Thanks. It works @aravindvnair99 Now you can close this issue |
Thanks for confirming @ssoad! |
Actually before the action waited for 0.3 seconds between the requests. Apparently if we return this wait, the execution time will skyrocket. |
We need to add a interim wait for between the subsequent api calls. Execution time I think should not affect anyone Its like a cron and it should take its own time to complete. |
Today I see another mistake. |
Hi guys, I'm sorry, but I'm getting this error from github again. |
Hi! Just wanting to add to this, that I also run into this rate limit for months now: |
I also have the same problem. Getting the new apikey from wakatime fixed the issue.. |
I'm receiving this as well, getting new API key and Github Token did not help.
|
Describe the bug
I find it difficult to describe what caused the bug. Apparently, some requests are executed too often, and it is necessary to add a pause between them.
To Reproduce
Just check this log
https://github.com/SemenMartynov/SemenMartynov/actions/runs/4421561355/jobs/7772242992
Expected behavior
To make everything work as it used to.)
Github repository link
If applicable, please share the Github repository link.
The text was updated successfully, but these errors were encountered: