Intermittent Quality Gate Timeout – “New analysis pending” for over 5 mins in Community Edition 2025

SonarQube Server / Community Build
1

Hi Team,

We are intermittently facing an issue where the SonarQube scanner gets stuck on the “Waiting for the analysis report to be processed” step for 5 minutes and then fails due to a timeout. This happens in our CI pipeline using SonarQube Community Build 2025.1.0.102122 (LTA).

Issue Details:

  • SonarQube Edition: Community Edition
  • Version: 2025.1 (build 102122, LTA release)
  • Scanner version: SonarScanner CLI 7.1.0.4889
  • Java version: 17.0.14 (Amazon)
  • OS: Linux (Azure-hosted runner)
  • Intermittent behavior: The issue does not occur in every run, which makes it harder to reproduce.

Log Snippet:
09:06:01.516 INFO Analysis report uploaded in 45ms
09:06:01.517 INFO ------------- Check Quality Gate status
09:06:01.518 INFO Waiting for the analysis report to be processed (max 300s)
…
09:11:02.081 ERROR Quality Gate check timeout exceeded
09:11:02.410 INFO EXECUTION FAILURE
09:11:02.411 INFO Total time: 5:21.326s
ERROR: Job failed: exit code 1

Questions:

  1. Is there any known performance or processing issue in SonarQube 2025.1 Community LTA version?
  2. Could this be related to background task queueing or DB latency?
  3. Are there recommended settings (e.g., increasing the timeout, tuning async processing) to mitigate this?

Let me know if you need more information (e.g., thread dumps or server logs). Appreciate your help!

Best regards,
Harish

2

Hey there.

This version does not exist. There is no longer an LTA version for the SonarQube Community Build.

If you are currently using v25.1 of SonarQube Community Build, you should upgrade to v25.6 to ensure you are on an active version.

Keep in mind that the Community Build processes tasks one at a time. If your CI pipeline is set to wait for the Quality Gate status, and it takes longer than 5 minutes for your analysis to start (plus processing time), you may hit a timeout.

If you regularly encounter this 5-minute timeout, consider increasing the timeout in your CI pipeline.

Additionally, review your background tasks to identify possible bottlenecks: Are there too many queued analyses, or are some analyses taking unusually long to complete?