We are getting blocked by this issue. Sonar team, please provide an update.
Template for a good new topic, formatted with Markdown:
- ALM used : GitHub
- CI system used : Github Actions
- Scanner command used when : Sonar-Scanner
- Languages of the repository : Javascript / Typwscript
- Steps to reproduce : every PR of the whole organization fall in waiting status.
- Potential workaround : can’t see any workaround
Our teams are reporting this issue since this morning (18 Sept 2023 10am).
This issue is likely starting to occur sometime between last Friday (15 Sept 2023) and this morning (18 Sept 2023). On our end, no change at all during the weekend.
- Test on CI have all passed, the sonar scan is completed, the quality gate is green.
- Github does not receive the status from SonarCloud. So every PR is blocked, waiting for the SonarCloud to report back.
1 Like
Same issue with azure devops quality gate 
1 Like
I integrated SonarCloud into my three repositories, but suddenly today, the Sonar quality gate status is not appearing in Azure PR. It has been stuck on ‘waiting’ for a long time, and I have tried re-queue multiple times. I have also verified that my PAT token is valid.
@Akash_Grover This seems to be the same issue as SonarCloud Stuck in ‘Waiting’ for Azure DevOps , where multiple people are reporting this issue. Could you post there as well?
Hi all,
I’ve combined related threads here, so that everyone gets the same update. 
We noticed a problem with this a couple hours ago and fixed it about an hour ago (sorry for the late notice).
It may take a while to work through the existing backlog, but feel free to cancel your current jobs and restart them.
Ann & the SonarCloud team
Thanks for your reply.
waiting for confirmation of the fix.
HI,
I have re-queue and recreate the PR. But issue still the same!!!
Thanks
Paras
Issue is still persisting after multiple requeues of our pipelines in Azure DevOps.
Our monitoring doesn’t see any current failures in the system and our test runs have returned successfully.
Can I get you each to create a new thread & provide all your details, including how you run analysis?
Thx,
Ann
Done so, here’s the thread: Azure DevOps Quality Gate not decorating pull requests - SonarCloud - Sonar Community (sonarsource.com)
1 Like
HI G Ann,
Sure,
here my scenario.
- My SonarCoud was working perfectly till morning
- Later in Azure DevOps Quality Gate Check stuck on waiting.
- I Checked with other projects, all project has the same issue
- I checked the PAT Token and verify it ( it was Valid )
- Check the Service Connection between Azure DevOps and SonarCLoud - Issue still the same
I tried with New PR and Re-queue options, issue still the same…
I have observed a discrepancy in the status update of our scanning results. Upon analyzing the situation, I’ve noticed that in SonarCloud, I can view the scanning results. However, in the Azure DevOps Pull Request (PR) overview, the status is not being updated as expected.
Also not seeing any improvements. Issue is still occurring with existing or new pull requests.
I’ve the same issue.
The PR build for new PRs are still stuck even today morning for us. Any update?
Same issue exactly since yesterday morning. Tried every step described by others in this thread, no results. The verbose logs in Azure DevOps for the Sonar steps in our pipelines shows a successful retrieval of the SonarCloud analysis results, but the quality gate remains in waiting status in our pull requests.
Also experiencing same missing quality-gate update problem since yesterday. I was hoping it would be fixed within 24 hours but sadly not this time
Same on our side. Things haven’t improved and we are having to manually check the sonar cloud reports to progress PRs. Do we need to raise another ticket or are the original details still good? Seems like it’s still a general issue, affecting multiple people.
Same here, on the PRs the status check for sonarcloud quality gates are not working. There are on a infinite waiting status, but on sonarcloud the pull request branch is analyzed correctly.
Hope this will fixed soon, because in the meanwhile it’s a manual step that the team should care, deactivating the status check for afet activating it again…
we are also facing same issue. Team please help.