Hi team, I’m running SonarCloud analysis through GitHub Actions using the official sonarqube-scan-action. The scan hangs indefinitely at 12 out of 13 source files, and never completes. Here’s what I see in the logs: 03:06:46.209 INFO SCM Publisher SCM provider for this project is: git 03:06:46.20…

Thank you very much, I’m keeping an eye on it.

Hi all, We are currently unable to reproduce this, and need more input. (See my earlier request for thread dumps .) In light of that, and since there’s a workaround: [image] G Ann Campbell: add -Dsonar.scm.use.blame.algorithm=GIT_FILES_BLAME to your analysis command Our current plan on this…

Hej Ann, We are facing the exact same issue since yesterday evening, but found this thread only now. Attached is a thread dump from one of our machines, hope it helps finding the root cause. sonar-scanner_thread_dump.txt (38.0 KB) Thanks for the workaround, worked like a charm. Best Regards, T…

We encountered exactly the same issue. However, after adding the parameter -Dsonar.scm.use.blame.algorithm=GIT_FILES_BLAME, it started working for us.

@ganncamp Hello, good morning. We’re still experiencing the same issue today, the file scan gets stuck. 13:54:30.985 INFO 12/13 source files have been analyzed

Hi @SoyRonyVargas , Can you try the workaround? [image] G Ann Campbell: add -Dsonar.scm.use.blame.algorithm=GIT_FILES_BLAME to your analysis command Ann

@ganncamp Yes, but does that have any different impact compared to not including it?

Hi, As you might guess from the parameter name, it uses a different blame algorithm than the default. I’m not briefed on the low-level differences. The idea was to unblock users. Ann

Hello Ann, We are also having the “analysing gets stuck at files” issue. The workaround is working for us with sonar.scm.use.blame.algorithm=GIT_FILES_BLAME Attached is our log file. sonarclouddump.txt (109.9 KB)

Hi ! confirmed workaround : ` name: SonarCloud Scan uses: SonarSource/sonarqube-scan-action@v5.2.0 env: SONAR_TOKEN: ${{ sonar-token }} with: args: > -Dsonar.verbose=true -Dsonar.scm.use.blame.algorithm=GIT_FILES_BLAME`

SonarCloud analysis gets stuck at 12/13 files

SonarQube Cloud

ganncamp (G Ann Campbell) July 14, 2025, 3:35pm 27

Hi @SoyRonyVargas,

Can you try the workaround?

Ann

SonarQube cloud not recognize pull request

Topic		Replies	Views
SonarQube scans erroring and not reporting meaningful results since last week SonarQube Cloud sonarqube , scanner , coverage , sonarqube-cloud	12	163	February 4, 2026
✖ SonarCloud analysis failed SonarQube Cloud php , scanner , bitbucket , sonarqube-cloud	22	8188	May 6, 2021
Sonar cloud stopped to display new pull requests SonarQube Cloud	18	709	July 31, 2023
Analysis not working - "AYKs1w7Ab4KfHGHnmaZw" SonarQube Cloud autoscan	1	329	August 18, 2022
GitHub Action scanning timing out SonarQube Cloud csharp , github-actions , bump , sonarqube-cloud	19	995	November 15, 2023

SonarCloud analysis gets stuck at 12/13 files

Related topics