SonarCloud has stopped analysing our repositories

We started seeing a message this morning on all of our organisation’s PRs on GitHub:

INFO: Check ALM binding of project 'redacted'
INFO: Detected project binding: NONEXISTENT
INFO: Check ALM binding of project 'redacted' (done) | time=418ms
INFO: Load project pull requests
INFO: Load project pull requests (done) | time=414ms
INFO: Load branch configuration
INFO: Github event: pull_request
INFO: Auto-configuring pull request 4176
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 10.264s
INFO: Final Memory: 20M/77M
INFO: ------------------------------------------------------------------------
ERROR: Error during SonarScanner execution
ERROR: Could not find a default branch for project with key 'redacted'. Make sure project exists.
ERROR: 
ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.

We have changed no settings over the weekend, the SONAR_TOKEN is valid and intact within our GitHub’s secrets. I have also deleted and re-added projects on SonarCloud itself and the analysis won’t automatically start like it usually does.

One of the latest failed analysis IDs is: 207d634f-1e67-4d57-ae24-43c5f196ee98

1 Like

Hi @mw-zac ,

Can I check how you are calling SonarCloud from Github? Are you using Github actions or are you using Automatic Analysis? I ask as I see an issue in the logs which looks like you are trying to use Automatic analysis however it might be disabled on the project in Sonarcloud.io

Can I also check which languages you are trying to analyse?

Using GitHub actions. You probably are seeing that automatic analysis issue because I did try that afterwards just to see if it changed anything.

We analyse TS and JS.

Just as a note it’s working now but the issue that originally presented itself is a weird one and would love to know if there’s anything that can be done in the future

Ah yes that would explain that error, we are investigating an issue at the moment, I will investigate further to see what could have been the cause. I am however glad that analysis is working for you now.