Project already imported

SonarQube Cloud
1

Hello SonarCloud Support Team,

I am experiencing an issue where a GitHub repository cannot be imported into our organization because SonarCloud flags it as already existing, yet the project is completely missing from our dashboards and search results.

Details of the issue:

Organization: Rova

Repository Name: rova-cba-routing-hub

The Problem: When navigating to the “Analyze projects” screen, the repository rova-cba-routing-hub is grayed out and labeled as “Already imported”. However, when searching the organization’s main Projects list, this repository/project does not appear anywhere.

Troubleshooting Performed: Checked filters (including analysis status and visibility).

Attempted to locate any “provisioned” or “never analyzed” states.

Attempted to search by both repository name and project key.

Verified the GitHub App configuration mapping.

It appears there may be a “ghost” record or an orphaned binding in the backend database mapping this repository to a project that is otherwise inaccessible or deleted.

Could you please help us locate this project, fix the permission/visibility state, or clear the existing binding from your backend so we can re-import it properly?

2

Hi,

I’ve moved your post to a new thread because the one you added it to was 8 months old.

It’s possible for even an Org admin to not have permissions to a project. Can you try to restore admin access to the project?

 
Thx,
Ann

3

Hello SonarCloud Support Team,

We are experiencing a database desync issue where a GitHub repository cannot be imported into our Team plan organization because SonarCloud marks it as “Already imported”, yet the project component key does not exist.

Please note that this is not a confusion with our other repository, rova-cba-fcmb-uk-routing-hub (which is active and working fine). This issue is specifically affecting the base repository listed below.

  • Organization Key: roava

  • Target Repo Blocked: rova-cba-routing-hub

Troubleshooting performed via Web API:

  1. We queried api/projects/search?organization=roava. The key for rova-cba-routing-hub is completely absent from the component list.

  2. We attempted to run api/projects/delete?project=roava_rova-cba-routing-hub and received a Component key not found error.

  3. We attempted to forcefully assign admin permissions via api/permissions/add_user to kickstart it, and it failed because the project key cannot be located.

The UI import wizard is completely blocked by an orphaned database mapping record linking our GitHub repository to a non-existent SonarCloud project key.

Could a backend engineer please manually drop or clear the orphaned repository binding/link for rova-cba-routing-hub in the roava organization database so that we can fresh-import it?

Thank you.

4

Hi Ann,

Troubleshooting performed via Web API:
We queried api/projects/search?organization=roava. The key for rova-cba-routing-hub is completely absent from the component list output.

  1. We attempted to run api/projects/delete?project=roava_rova-cba-routing-hub and received a Component key not found error.

  2. We attempted to forcefully assign admin permissions via api/permissions/add_user to kickstart it, and it failed because the project key cannot be located.

The UI import wizard is completely blocked by an orphaned database mapping record linking our GitHub repository to a non-existent SonarCloud project key. Could you please clear or remove the broken GitHub repository binding on your end for rova-cba-routing-hub so we can re-import the project freshly?

Thank you!

6

Hi,

Thanks for checking. I’ve flagged this for folks with better access than I have.

 
Ann

7

Thanks Ann. Will be on standby for updates.