Azure DevOps in waiting status

We are experiencing an issue where the Sonar quality gate on our PR remains in the “waiting” state long after the analysis has completed. We have confirmed that the PAT is valid. This issue has been occurring since 03/03/2025.

log:


2025-03-04T21:28:41.2950826Z INFO: Importing 3 Roslyn reports
2025-03-04T21:28:41.3688709Z INFO: Found 3 MSBuild C# projects: 1 TEST project. 2 with no MAIN nor TEST files.
2025-03-04T21:28:41.3689433Z INFO: Sensor C# [csharpenterprise] (done) | time=516ms
2025-03-04T21:28:41.3689757Z INFO: Sensor Analysis Warnings import [csharpenterprise]
2025-03-04T21:28:41.3723792Z INFO: Sensor Analysis Warnings import [csharpenterprise] (done) | time=0ms
2025-03-04T21:28:41.3724499Z INFO: Sensor C# File Caching Sensor [csharpenterprise]
2025-03-04T21:28:41.3724832Z INFO: Sensor C# File Caching Sensor [csharpenterprise] (done) | time=0ms
2025-03-04T21:28:41.3725180Z INFO: Sensor C# Tests Coverage Report Import [csharpenterprise]
2025-03-04T21:28:41.3854785Z INFO: Parsing the OpenCover report C:\a\1\s\TestResults\319f27a2-2742-467f-8ff9-2fda3058c350\coverage.opencover.xml
2025-03-04T21:28:41.5753381Z INFO: Adding this code coverage report to the cache for later reuse: C:\a\1\s\TestResults\319f27a2-2742-467f-8ff9-2fda3058c350\coverage.opencover.xml
2025-03-04T21:28:41.5757182Z INFO: Sensor C# Tests Coverage Report Import [csharpenterprise] (done) | time=203ms
2025-03-04T21:28:41.5760077Z INFO: Sensor C# Unit Test Results Import [csharpenterprise]
2025-03-04T21:28:41.5789101Z INFO: Parsing the Visual Studio Test Results file 'C:\a\1\s\TestResults\AzDevOps_vmss-devo0000BD_2025-03-04_21_27_16.trx'.
2025-03-04T21:28:41.7648386Z INFO: Sensor C# Unit Test Results Import [csharpenterprise] (done) | time=188ms
2025-03-04T21:28:41.7648916Z INFO: Sensor JsArchitectureSensor [architecture]
2025-03-04T21:28:41.7804653Z INFO: Reading SonarArchitecture IR data from directory "C:\a\1\.sonarqube\out\.sonar\architecture\js"
2025-03-04T21:28:41.7844594Z INFO: * Protobuf reading complete | memory total=192 | free=104 | used=87 (MB)
2025-03-04T21:28:41.7849693Z INFO: * Export complete | memory total=192 | free=102 | used=89 (MB)
2025-03-04T21:28:41.7850188Z INFO: Sensor JsArchitectureSensor [architecture] (done) | time=15ms
2025-03-04T21:28:41.7852111Z INFO: Sensor Zero Coverage Sensor
2025-03-04T21:28:41.7854832Z INFO: Sensor Zero Coverage Sensor (done) | time=0ms
2025-03-04T21:28:41.7893078Z INFO: SCM Publisher SCM provider for this project is: git
2025-03-04T21:28:41.7903075Z INFO: SCM Publisher 23 source files to be analyzed
2025-03-04T21:28:42.4623159Z INFO: SCM Publisher 23/23 source files have been analyzed (done) | time=666ms
2025-03-04T21:28:42.4650220Z INFO: CPD Executor Calculating CPD for 0 files
2025-03-04T21:28:42.4652224Z INFO: CPD Executor CPD calculation finished (done) | time=0ms
2025-03-04T21:28:42.6012481Z INFO: SCM writing changed lines
2025-03-04T21:28:42.8622237Z INFO: SCM writing changed lines (done) | time=265ms
2025-03-04T21:28:43.4395980Z INFO: Analysis report generated in 953ms, dir size=513 KB
2025-03-04T21:28:43.5566837Z INFO: Analysis report compressed in 110ms, zip size=162 KB
2025-03-04T21:28:44.3705108Z INFO: Analysis report uploaded in 813ms
2025-03-04T21:28:44.3730781Z INFO: ANALYSIS SUCCESSFUL, you can find the results at: https://sonarcloud.io/dashboard?id=truevelocity_TrueVelocity.Web.Api.Admin&pullRequest=3035
2025-03-04T21:28:44.3731406Z INFO: Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report
2025-03-04T21:28:44.3731870Z INFO: More about the report processing at https://sonarcloud.io/api/ce/task?id=AZVjD6PnZ3rQ5lq7Mn_W
2025-03-04T21:28:44.3817850Z INFO: Time spent writing ucfgs 0ms
2025-03-04T21:28:44.5479197Z INFO: Analysis total time: 43.392 s
2025-03-04T21:28:44.5497810Z INFO: ------------------------------------------------------------------------
2025-03-04T21:28:44.5498173Z INFO: EXECUTION SUCCESS
2025-03-04T21:28:44.5499341Z INFO: ------------------------------------------------------------------------
2025-03-04T21:28:44.5499950Z INFO: Total time: 50.265s
2025-03-04T21:28:44.6148183Z INFO: Final Memory: 31M/120M
2025-03-04T21:28:44.6149380Z INFO: ------------------------------------------------------------------------
2025-03-04T21:28:45.0102435Z The SonarScanner CLI has finished
2025-03-04T21:28:45.0108062Z 21:28:44.997  Post-processing succeeded.
2025-03-04T21:28:45.0351169Z ##[section]Finishing: Run Sonar Analysis

Hey there.

I can confirm that in the backend, the error being thrown is The Azure DevOps access token is not valid!

Have you double chcked that the token set in your global Administration > Organization Settings > Organization binding is valid, and any token configured at the project-level Administration > General Settings > Pull Requests)?

Thanks, Colin. We did. However, we updated both the pull request and the organization binding to use the same PAT. They were each using different valid tokens, but setting them to use the same token resolved the issue.