Dependabot daily job fail - "Update check cancelled' error #58844
-
Select Topic AreaBug Bodyhi folks, In my org, on all my private repos (~ 50 repos) i setup a basic dependabot.yaml which checks daily for If i trigger the jobs manually they all run successful and i can see the logs. However getting triggered daily is a hit and miss, mostly miss with the below error. Since i have no clue how to troubleshoot, anyone from dependabot team can chime in please? There are no logs, speaking with GH org admin, no clue where to dive in (not is a hosted org in github.com not GH enterprise server), how do you go and troubleshoot? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Hi folks, any chance someone from the dev eng team might provide some insights as to where to dig next ? |
Beta Was this translation helpful? Give feedback.
-
Having the exact same issue. Any info appreciated. |
Beta Was this translation helpful? Give feedback.
-
Hi 👋🏾 I'm an engineer on the Dependabot Updates team and I think I may have tracked down a cause for this error. I think if you have your Dependabot update configs scheduled for the same time across a lot of repos our backend sees it as spammy and ends up rate limiting the the entire org. I would recommend either (1) configuring your Dependabot version updates to run at different times, or (2) forego setting a time in your Dependabot configs altogether so that Dependabot can run updates across the scheduled day. I will look into how we can mitigate this issue on our end, and please let me know if this helps! |
Beta Was this translation helpful? Give feedback.
-
this issue has been solved back in July |
Beta Was this translation helpful? Give feedback.
-
This is happening to us. We have 5 repos set to interval: monthly. Only 2 of them succeed |
Beta Was this translation helpful? Give feedback.
Update on this: we had a support engineer confirm that changing the update schedule has no affect and is still seeing "update check cancelled" errors.
We will be automatically retrying some of these update check jobs on our backend instead of cancelling the job when we encounter this error, so you should see more successful runs.