After the incident reported here: https://status.sonarqube.com/incidents/p52gpbpk23y5, our GitHub Actions CI checks were working again for a short time, but since yesterday the analysis step has been failing.
SonarCloud Code Analysis: Cancelled after 6s — SonarQube Cloud analysis failed
Please retry analysis of this Pull-Request directly on SonarQube Cloud
We’re on the Team plan and no limits seem to be reached.
Is anyone else seeing this on GitHub Actions? Any insight or workaround would be appreciated.
Do you see any error details associated to the background task under your project-level Administration > Background tasks? You should be able to see Show error details under the actions menu.
Thanks for your reply @Colin. The issue was hitting a plan limit on Lines of Code. We fixed it, but could the error message be more specific? Developers don’t have admin access to the dashboard, so clearer messaging would help troubleshooting.
Ran into the same confusion in our setup. Started receiving the
Please retry analysis of this Pull-Request directly on SonarQube Cloud
on our SonarCloud GHA checks. Most developers / users of SonarCloud do not have admin access, so were unaware the cause was a plan limit on Lines of Code. More descriptive error messaging on what the analysis is failing would be helpful.
Also, is this new behavior where analysis on existing repos fails when line limits are reached? As far as I remember, when this came up for our team last year, the behavior was no new repos could be added. But existing repo analysis did not fail when monthly limit was reached.
To my knowledge, this has always been the case. I’m not aware of any instance where SonarQube Cloud has allowed analyses to exceed the organization’s line of code (LoC) limit. The behavior you’re seeing is consistent with how it’s typically worked.
