Template for a good new topic, formatted with Markdown:
ALM used (GitHub)
CI system used (Github Actions)
Scanner command used when applicable (private details masked)
Languages of the repository : TypeScript
Only if the SonarCloud project is public, the URL
And if you need help with pull request decoration, then the URL to the PR too
Error observed :
"errorMessage": "Fail to process issues of component 'ab-inbev-analytics_test-and-learn-v2-UI:src/elements/FormSwitchField.tsx' (Visit of Component {key=ab-inbev-analytics_test-and-learn-v2-UI:src/elements/FormSwitchField.tsx,type=FILE} failed)",
Steps to reproduce : simple scan using sonar cloud that’s it.
Can you provide the approximate date/timestamp of this error? That will make it easier to find in our logs. And where are you seeing the “Fail to process issues…” message?
Are you using automatic analysis or CI-based analysis? And if the latter, can you provide your analysis log?
The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.
We are using CI-Based analysis using Github Action. We have attached latest zip file for the log archive. We have changed few code and now the error is coming in different file
Hello Team
Please find the attached log and we have tested with other things and new analysis ID is generated so please have a look. This is creating issue even though coverage works fine on our system.
2025-05-08T12:46:05.9421158Z 12:46:05.941 INFO Analysis report generated in /home/runner/work/test-and-learn-v2-UI/test-and-learn-v2-UI/.scannerwork/scanner-report
2025-05-08T12:46:05.9426164Z 12:46:05.942 DEBUG Upload report
2025-05-08T12:46:05.9445839Z 12:46:05.944 DEBUG --> POST https://sonarcloud.io/api/ce/submit?organization=ab-inbev-analytics&projectKey=ab-inbev-analytics_test-and-learn-v2-UI&projectName=test-and-learn-v2-UI&characteristic=branch%3Ddevelop&characteristic=branchType%3DLONG (2630649-byte body)
2025-05-08T12:46:11.9167501Z 12:46:11.916 DEBUG <-- 200 https://sonarcloud.io/api/ce/submit?organization=ab-inbev-analytics&projectKey=ab-inbev-analytics_test-and-learn-v2-UI&projectName=test-and-learn-v2-UI&characteristic=branch%3Ddevelop&characteristic=branchType%3DLONG (5972ms, 44-byte body)
2025-05-08T12:46:11.9184809Z 12:46:11.918 INFO Analysis report uploaded in 5977ms
2025-05-08T12:46:11.9198436Z 12:46:11.919 DEBUG Report metadata written to /home/runner/work/test-and-learn-v2-UI/test-and-learn-v2-UI/.scannerwork/report-task.txt
2025-05-08T12:46:11.9200042Z 12:46:11.919 INFO ANALYSIS SUCCESSFUL, you can find the results at: https://sonarcloud.io/dashboard?id=ab-inbev-analytics_test-and-learn-v2-UI&branch=develop
2025-05-08T12:46:11.9201528Z 12:46:11.919 INFO Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report
2025-05-08T12:46:11.9204952Z 12:46:11.920 INFO More about the report processing at https://sonarcloud.io/api/ce/task?id=AZav7pkGxgecsER1cjSa
These are few logs time which you can see in this file. do suggest us if anything from our end if you need.
read last line after analysis successful there are some processing is happening which are tracked in different URL which is failing and due to that I am not able to see analysis on my sonar cloud. I have separately paste that URL as well.
Due to that our report is not updating see we have analysis 26 days ago, which was last here after that we are facing issues in analysis and not available over platform.
Even though we are running every day this analysis using pipeline.
Okay, you’re saying that server-side processing of your analysis is failing, right?
In that case, I need you to check the project’s Administration → Background Tasks. You should see a row there with a Failed status. On the right side of that row is a 3-dots menu that should show you the error.
Edit: I see from the screenshot you’ve edited in to your post that you don’t have administration rights on this project. You’ll need to ask someone who does.
Thanks for the updated details.
I could track down the issue to a strange behavior that we did not observe since 2021, and that we failed to explain at that time by lack of data.
We will investigate and get back to you - We will do our best and it might take some time.
