The last analysis has failed

SonarQube Cloud
1

Automatic analysis failing on every push since Sep 17 — three failure IDs, including two after the incident was resolved

Organization interdevme, project interdevme_App: private, free plan, Azure DevOps, automatic analysis on the main branch dev.

The last successful analysis was of commit a188437 (2026-09-17 15:02 UTC). Every push to dev since then has failed:

Push Time (UTC) Failing analysis ID
3753246 2026-09-17 19:44 9e0c2de4-449e-414f-bd1a-7d49f6485672
8ba33a8 2026-09-18 10:26 aee2a7b3-0bae-4869-9474-4cc55774e9b7
2d0ef1c 2026-09-18 11:33 05d34b9d-2c0d-4320-8255-13a919bcf1bb

The first failure happened during the incident “Increased errors affecting analysis and CI” (resolved 2026-09-17 20:08 UTC). The other two came 14–15 hours after it was resolved, so I don’t think the incident explains them.

On the Azure DevOps side everything looks healthy: the three service hooks are enabled, every delivery shows succeeded, and sonar.autoscan.enabled is true.

One change on our side that may help you line up the logs: on Sep 17 I changed the project’s language settings so that .sql files are analyzed as T-SQL, and removed the PL/SQL settings. The repository has 37 .sql files.

Could you check the logs for these three IDs and tell me what is making the analysis fail?

2

It keeps failing. Can someone please help me?

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: 0be45c8c-1df7-4ecd-8e76-5e3b62ce0835.

3

Hey @Ricardo_Gaefke, welcome to the Community!

I had a look at the logs for these analysis and it seems like:

ERROR: Language of file 'database/Error/Error.sql' can not be decided as the file matches patterns of both sonar.lang.patterns.plsql : **/*.sql,**/*.tab,**/*.pkb and sonar.lang.patterns.tsql : **/*.sql

It looks like you configured file-language-detection patterns in a way that our Scanner doesn’t like… This issue is not uncommon (we mention it in our docs), the bottom line is that there are 2 places you should check for this misconfiguration:

  • The UI: go to the project’s Administration > General Settings > Languages > PL/SQL, and also T-SQL settings.
  • A .sonarcloud.properties file in your project’s root > sonar.lang.patterns.tsql and sonar.lang.patterns.plsql properties.
4

Thank you very much. I had removed Oracle from validation but it was not enough… so I added Oracle as .plsql and it worked.