SonarCloud/quality gate is waiting forever in pull requests

  • ALM used (Azure DevOps)
  • CI system used (Azure DevOps)
  • Scanner command used when applicable (private details masked)
   - task: SonarCloudPrepare@1
         SonarCloud: ‘’
         organization: ‘’
         scannerMode: ‘MSBuild’
         projectKey: ‘’
         extraProperties: |
  - task: SonarCloudAnalyze@1
  - task: SonarCloudPublish@1
  • Languages of the repository

    • C#
  • Only if the SonarCloud project is public, the URL

    • The project is private
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)

    Waiting task

  • Steps to reproduce

    • Pipeline tasks work normally, the result is published to SonarCloud but does not transmit to Azure DevOps
    • Token is valid according to SonarCloud
  • Potential workaround

    • At the beginning of the month, I was experiencing this same error where the token was invalid.
      To solve this problem, I changed the token and remade the project on SonarCloud. However, it’s not feasible to change the token and redo the project every time, so I would like to know if there is a viable solution.

Hey there.

Thanks for the report. I suggest following this thread:

A post was split to a new topic: Pipeline stalled waiting for QG status

2 posts were merged into an existing topic: Pipeline stalled waiting for QG status

Hello G Ann Campbell, the error had been resolved, but this morning it occurred again


To be clear, you’re seeing analysis succeed, but the pipeline is stalled waiting for the Quality Gate status?

Do you see the PR in SonarCloud?


Yes, it’s complete in Sonar, but here it still shows as waiting in DevOps. I’m sending pictures to explain.
here is the pull request in SonarCloud:

And here is in Azure DevOps:


Thanks for the details. I’ve flagged this for the team.


Hello @Joao_Miziara.

This issue has been fixed in the past week, and we haven’t observed it.
Can you please confirm if you are still experiencing this issue?


Hello Andrey Luiz, I apologize for the delay, but the issue has been resolved. Thank you for your assistance.