some repositories are disabled, for no obvious reason

[vincent-fuchs]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

No response

Please tell us more about your question or problem

Hi,

I have noticed a couple of repositories in my org are disabled but it's not clear why. Also, we can't filter on the renovate status only in the UI, so I am not able to tell how many impacted. I become aware of it when developers contact me asking why renovate doesn't seem to be enabled on their repository.

for instance :

the repository is still seen, as we see a last updated as of today

if I trigger it manually, it gets things rolling (I tried it on another repository).. but I'd like to avoid that workaround.

the renovate.json file has been there for several weeks

and I don't see any PR by Renovate either closed or open.

the only info I found is an old github comment that says that when it's disabled, the status is checked once a day. I don't know if the problem is that it checks it but doesn't see anything to trigger, or if it doesn't check it at all.

Is it possible to know what could have cause the repository status to become disabled ? is it normal that it doesn't start again automatically ?

worst case, can I easily get the list of disabled repositories, so that I can trigger them manually ?

Thanks

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[jamietanna]

Can you please share a Job ID from one of the repos (or a repo name) so we (Mend) can check? A Job ID is safe to share publicly, if you can find one from a repo that has been processed

[vincent-fuchs]

this is a job ID on one of the repositories where it now works (after I triggered a scan manually, 10 days ago) : 019c1d70-81ce-73c5-b0a6-9872492ff6c7

I can give you privately the name of the repositories that are disabled

[jamietanna]

Unfortunately I can't see what was the reasoning that the repo for Job ID, from this point in time

I can see you org has many disabled for what looks like valid reasons (empty, no-package-files, etc) - happy for you to share privately to my email address if there are other repos you're wondering about!

[vincent-fuchs]

I checked again on the repositories I had found initially, and none of them are disabled anymore - some of them are onboarding now.

the UI doesn't allow to filter on status (on the whole list) and sort by latest activity, so it's difficult for me to confirm if I still have the problem or not. If that filtering was possible, I would easily be able to see if a repository that had a recent commit is also disabled in renovate while it should not.

[project0]

I have the same problem, renovate is enabled, but status is disabled without activating itself. I do not understand how the status can be disabled with renovate being enabled. This is very confusing and also does not explain why it has been disabled anyway.

[jamietanna]

@project0 mind sharing a Job ID for one of the repos? (Or a repo name, if you're happy sharing publicly)

[project0]

There are no job-ids, i mean they do not run at all once status is disabled (even tough it is Enabled).

but, a repo for example flowers-software/github-actions

[webdevbynight]

Hello,

I am facing the same problem as @vincent-fuchs and @project0: two of my repositories using Renovate have Renovate enabled, but have their Renovate status set at disabled (I discovered it today); in addition, each one of these two repositories has a job with a status “Failed” and a mention of “application error” (job IDs: 019cdf6a-667a-770a-b4d6-b1faeb116152 and 019cdf6a-66c2-7bbb-896c-224672b287fc).

[project0]

We boiled down the problem in our case to the global organization setting toggle Dependency Updates, once its disabled and re-enabled all repos stuck in this disabled state :-(.