We are currently unable to see our projects in the Sonar dashboard

SonarQube Cloud
,
1

Previously, we are experiencing a payment processing error preventing us from unsuspending our SonarCloud organization. But after that, we managed successfully to completed the payment, but we are currently unable to see our projects in the Sonar dashboard. Help us how to restore project access.

2

Hi,

Welcome to the community and thanks for this report!

Could you provide your organization Id, please?

 
Thx,
Ann

4

My organization Id is uvation

5

Kindly provide a resolution at the earliest, as our organization has been unable to access SonarQube Cloud for the past three days despite completing the payment and having the account unsuspended.

6

Hi,

Thanks for your org Id. I’ve flagged this for the team.

 
Ann

7

Hi,

Let us know if there is any update

8

Hi,

Could you share what you do see in the dashboard?

 
Thx,
Ann

10

image
image1887×858 70.1 KB

image
image1880×847 59.3 KB

As a workaround, we manually re-created the same projects in same organization but using new project names (eg: previously the project name was chatbot, we manually created it as Uvation Web Services / chatbot-be) and generated new SonarCloud project keys.

12

Hi,

If you were able to (re-)import the projects, that suggests they didn’t exist on SonarQube Cloud.

Since you’ve got the projects onboard and accessible now, do you consider this resolved?

 
Ann

13

Issue Explanation & Clarification

After our SonarCloud organization (uvation) was unsuspended post-payment, we noticed that existing projects were not visible in the SonarCloud dashboard.

Although the organization status showed as active, previously imported projects (for example:
uvation / chatbot-be, uvation / identity-be) were not listed under Projects, which blocked us from managing PR analysis and quality gates.

What We Observed

  • When navigating to My Projects → Import repositories, some repositories appeared as:

    • Uvation Web Services / APIM → selectable

    • Uvation Web Services / chatbot-be → shown as Already imported but grayed out

  • Even though the repository was marked as Already imported, the corresponding project was not visible in the Projects dashboard.

  • This created a mismatch where:

    • SonarCloud believed the project already existed

    • But the project was not accessible or visible in the UI

Workaround We Applied

Since we did not receive an immediate resolution and PR validations were blocked, we implemented a workaround to unblock development:

  • Manually created new SonarCloud projects using Create project manually

  • Renamed the projects to a new namespace format, for example:

    • Uvation Web Services / chatbot-be

    • Uvation Web Services / identity-be

  • Updated the Sonar project keys in Azure DevOps pipelines to point to these newly created projects

  • This allowed:

    • PR analysis to work again

    • Quality Gates to be evaluated

    • Pipelines to proceed without blocking development

Clarification Requested

While the workaround is functional, we would like to understand the root cause:

  • Why were existing projects not visible after the organization was unsuspended?

  • Why did SonarCloud show repositories as Already imported but not display the corresponding projects?

  • Is there a backend sync or recovery step required after billing suspension is lifted?

Understanding this will help us avoid similar issues in the future and determine whether any cleanup or reconciliation is needed for the manually created projects.

image
image1877×859 71.2 KB

image
image1875×845 63.4 KB

14

Hi,

Thanks for the thorough writeup. This point is key to my understanding:

At this point, I’m not sure how to continue, so I’m going to flag this for folks with back-end access.

 
Ann

16

Hi Ann,

Thank you for looking into this and for flagging it to the back-end team.

To clarify the point you highlighted:
We used “Create project manually” as a temporary workaround because the existing projects were not visible in the dashboard, even though they were marked as already imported. This was done only to unblock PR analysis and pipeline validations while we awaited guidance.

1 Like
17

Let us if there is any update regarding this

18

Hi,

Sorry, but I don’t have anything for you yet.

 
Ann

19

Hi,

I’m following up on the issue we reported last week regarding our projects not being visible in the Sonar dashboard. Unfortunately, we have not received any response or actionable guidance so far.

We are using the paid version of Sonar, and this lack of timely support is concerning—especially since Sonar is a critical part of our PR validation process across the organization. This issue directly impacted our development workflow.

Due to the absence of support, our team had to implement a workaround and resolve the issue on our own. However, this is not a sustainable approach. We need to understand:

  • The root cause of this issue

  • Whether this is a known problem

  • What the recommended fix is if it happens again

  • What preventive measures we can put in place

Given the importance of this tool in our CI/CD and quality gates, we expect a clear explanation and guidance to avoid a recurrence.

Please treat this as a priority and get back to us with a proper resolution and next steps.

Looking forward to your response.

Best regards,
Bharath