SonarQube quality gate timeout waiting for the result in CI

With sonar.qualitygate.wait=true, the scanner submits the analysis then polls the server for the gate result. If background processing (the compute engine) is slow, the poll exceeds the timeout and the step fails without a verdict.

What this error means

The step fails with a message that it timed out waiting for the quality gate, for example "QUALITY GATE STATUS: NONE" or the action reporting it exceeded the wait timeout, while the analysis is still processing on the server.

sonar-scanner

INFO: Waiting for the analysis report to be processed (max 300s)
ERROR: Time limit reached, the report is still being processed. Aborting.

Common causes

The compute engine backlog delays the result

A busy SonarQube server queues analysis reports; the gate result is not ready before the default wait timeout elapses.

The wait timeout is too short for this project

Large projects take longer to process, so the default poll window is not enough time to get a verdict.

How to fix it

Raise the gate wait timeout

Increase the timeout so the poll covers normal processing time.
Keep waiting enabled so the gate still blocks on real failures.
Re-run and confirm the verdict arrives within the window.

Terminal

sonar-scanner \
  -Dsonar.qualitygate.wait=true \
  -Dsonar.qualitygate.timeout=600

Address a chronically slow compute engine

If the server is consistently backlogged, scale it or reduce concurrent analyses so gate results return promptly. Retrying alone will not fix a saturated compute engine.

How to prevent it

Set sonar.qualitygate.timeout to cover your largest project.
Keep the SonarQube compute engine sized for peak analysis load.
Monitor the background task queue for persistent backlog.