SonarCloud error: key already exist while creating new project

We are using SonarCloud task on Azure to create new project and new key e.g. “app-service”.
If for some reason project creation fail, we are not able to see that project while login to SonarCloud page, but we are also not able to create manually project again from the sonracloud.io, instead we getting error:
"Could not create Project, key already exist: app-service"
I’ve checked all existing projects and none of them contain that key.

Hi,

Project keys are, for now, global across the whole SonarCloud database, so this project key might exist in a private Organization, that’s the reason why you are not seeing it.

Mickaël

Hello,
We are facing the same issue: a project key is not duplicated in our organization’s (maven) projects, but still we get the error message that the key already exists.
So, that means that a customer’s project key is validated for uniqueness against all the project keys of all the customers ?
And if yes, what is the solution for a new (er) customer? As far I can understand, to change the project names/artifacts he is currently using (until he does not get the message) ?
Thanks

This is not only funny but also a bit disappointing coming from a large platform like Sonarcloud. Why should we care about project keys used by other organisations or customers of yours?

The convention we follow is to keep project key exact as the project repository name on Github. Your constraint is making it difficult to follow the convention we want to.

1 Like

Alternatively you should atleast make the error message obvious enough to understand that the key is already taken by projects of other organisation(s). Why mislead the users into thinking that a project was created by them with this key when they did not?

1 Like