Last analysis has failed: 41135ee0-00b8-4e95-8589-05dc3195a653 - Error Analysis status

Could you help us pls?

The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: 41135ee0-00b8-4e95-8589-05dc3195a653.

Hi @hectoro_backbase,

We are investigating increased error rates affecting the SonarQube Cloud web experience, Automatic Analysis, and CI-based analysis. Some customers may experience failed or delayed analyses.

Our engineering teams have identified the cause and working to restore normal service. We will provide another update as soon as more information is available.

You can track the status of this incident here: SonarQube Status - Increased errors affecting analysis and CI.

1 Like

2d22055a-eedc-47db-b6bb-d6105b99cc4f

This incident is now resolved.

Resolved — We have resolved an issue that caused elevated errors and slower processing for Auto Scan and CI analyses.

Processing performance has returned to normal.

We will continue to monitor the service and are completing follow-up work to prevent recurrence. We apologize for the disruption.
Posted 5 minutes ago. Sep 17, 2026 - 20:08 UTC

Mine still says it’s failed. How do we trigger a new scan?

Is there a way to do so without a new committ?

Hey @celkins111, there’s no way to re-trigger it manually, you need to push a dummy commit. Try something like:

git commit --allow-empty -m "Trigger re-analysis"
git push