`ERROR Project not found.` Unexpected errors affecting organization

[sandupetrasco]

Hello team!

We are having a Sonar issue that impacts multiple pipelines & development process in our organization, with a lot of

ERROR Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, or contact the project administrator to check the permissions of the user the token belongs to

errors being thrown even tho the projects used in pipelines are existing in our Sonar organization.

We had the Azure DevOps Service Connections (SCs) updated with a new Sonar token, but this wasn’t enough. For the Service Connection creator, we added the Execute Analysis permission on the Sonar Project, and only after that did it start working. It’s worth mentioning that this did not happen for one or two projects that we might have had misconfigured, but the issue had a significant impact that affected multiple projects (having different SC owners) unexpectedly, starting about 1 day ago.

We are curious to understand what caused these issues, or if any regression/change existed on your side on how the Sonar analysis is done and pushed into SonarCloud.
Thanks!

• ALM used - GitHub
• CI system used - Azure DevOps, GitHub Actions

[Colin]

Unfortunately, I still have to be a bit vague. However, you’re not the only user who ran into an issue!

SonarCloud API returns "Project doesn't exist" (404) for projects that exist in the UI

Hey there. There’s a bit more to this story than I’m letting on right now (@tcs-cclaflin you’re right, something did change). In the meantime, please ensure that the appropriate permissions have been assigned to the relevant user(s) or group(s), either at the global or project level. @Rafael_Couto: For you, ensure that the Browse Project permission is granted at the project level for the projects you’re querying GET api/measures/component_tree You can always double-check the API calls you’re…

I hope we can share more soon.

[sandupetrasco]

Thanks!
Please let us know if you have any updates on this.

[Colin]

To close the loop here:

Important Security Update: Removal of the “Anyone” Group

Dear community, As part of our commitment to keeping your organization’s data secure, we are removing the Anyone group from SonarQube Cloud. The Anyone group was not aligned to the explicit Members group model and did not effectively communicate who was granted access when in use. The removal of the Anyone group is a proactive security measure – we’d like to assure you that we haven’t identified any exploitation of this group by malicious users. What’s changing: The Anyone group will no long…