The request cannot be processed. Try again later. - Issues importing/creating projects

SonarQube Cloud
1

TL;DR: We can’t import repos on a new organization (using GitHub as the ALM), the error shown is "The request cannot be processed. Try again later.". If we try to “Create project manually”, then we get the error "No organization for key 'xxxxxx-xxx-xxxx' (redacted key)"

Context:

  1. We are already using SonarQube Cloud with Gitlab. We are moving some repos from Gitlab to GitHub. As part of the process, we set up a new SonarQube organization on GitHub that is linked to our GitHub Organization.
  2. We are unable to add any projects to that new SonarQube organization, even though the connection to the GitHub Organization seems to exist.
  3. When we try to import it directly, we get the error show in Image 1.
  4. When we attempt to create a dummy project we get the error in Image 2.
  5. Similar error appears when going to the “Organization Binding” page under “Administration”. Image 3
  6. The App installation on the GitHub side seems to have all the permissions required. Image 4.
  7. We haven’t tried “suspending” the app installation, as not sure if undoing the binding might cause issues to reapply the biding later.
  8. The SonarQube Organization was created a while ago by a GitHub user that no longer exists. And we recently requested the admin role to be transferred to other user

Has anyone seen something similar? Is it safe to Suspend or Uninstall the app on GitHub to later redo the connection on SonarQube Cloud?

If there’s a better way to get direct support for this please let us know.

Image 1

image
image2910×1742 224 KB

Image 2

image
image2912×1738 377 KB

Image 3

(Had to delete this image as there’s a limit for new users on this forum). Same error of “Try again later” on the org biding screen.

Image 4

image
image2860×1728 404 KB

2

Hello @gerson-rojas-cdpy,

Thanks for the detail. The two errors together point to the same underlying issue: the SonarQube Cloud organization has lost its valid connection to GitHub, most likely because the GitHub account that originally set up the integration no longer exists. This can leave the organization binding in a broken state that isn’t straightforward to self-repair, so I’ll flag this for our development team to look into on the backend.

A few questions for you:

  1. Was the deleted GitHub account the one that originally installed the SonarQube Cloud GitHub App on your GitHub organization, or just the person who created the SonarQube Cloud organization? (These can be different.)
  2. Can you access other parts of your SonarQube Cloud organization without errors, e.g. members, settings, quality gates or is the error appearing more broadly?
  3. What does the ‘Organization Binding’ page currently show? Is the GitHub organization still listed there, or does it appear blank/unbound?

We’ll also need your SonarQube Cloud organization key to investigate. If you’d prefer to share that privately rather than in the thread, just let me know and I can reach out to you directly.