Repository navigation
[Bug][Sonarqube] Missing endpoint /api/users/search in Sonarcloud #8812
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
since yesterday collecting the data from sonarcloud projects stopped working due to /api/users/search endpoint returning 404:
Error running pipeline 9. Wraps: (2) Error running task 69. | Wraps: (2) subtask CollectAccounts ended unexpectedly | Wraps: (3) Error waiting for async Collector execution | Wraps: (4) Retry exceeded 3 times calling users/search. The last error was: Http DoAsync error calling [method:GET path:users/search query:map[p:[1] ps:[100]]]. Response: {"errors":[{"msg":"Unknown url : /api/users/search"}]} (404) | Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *errors.errorString Error types: (1) *hintdetail.withDetail (2) *errors.errorString
What do you expect to happen
collecting the data for the sonarcloud project is successful
How to reproduce
- add a sonarqube connection
- select sonarcloud
- target your project
- add token
- save and add to your project, hit collect
Anything else
No response
Version
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
dosubot commentedon Mar 26, 2026
Hi @psturc! I'm Dosu and I’m helping the incubator-devlake team.
This looks like a genuine compatibility issue between SonarCloud and SonarQube APIs. The
CollectAccountssubtask uses the/api/users/searchendpoint for both SonarCloud and SonarQube without differentiation. Based on your error, SonarCloud doesn't expose this endpoint at all (hence the 404), while SonarQube self-hosted does.This is similar to a recently fixed issue (#8731) where
/api/projects/searchwasn't available on SonarCloud and had to be replaced with/api/components/search_projects. The same pattern may need to be applied here—either find an alternative SonarCloud endpoint for users or make theCollectAccountssubtask optional/conditional for SonarCloud.Workaround: If you're using the API/Blueprint mode, you might be able to skip the
CollectAccountssubtask in your pipeline configuration. However, this may affect user-related data in your dashboards.To reply, just mention @dosu.
Docs are dead. Just use Dosu.