Code coverage suddenly dropped without any changes in code

[urvari18 (urvari)]

• ALM used Azure DevOps
• CI system used Azure DevOps
• Scanner command used when applicable (private details masked)
• Languages of the repository => .Net

Code coverage has been suddenly dropped without any changes in code
for all the application
for scanning the code we are using SONARWAY default quality profile

Example 01 :

Example 02 :

[Colin]

What do the logs say about importing code coverage?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube / SonarCloud, the first place you should look is the scanner logs. Where do I find the scanner logs? This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the scanners, either directly or wrapped by one of many integrations, such as the SonarScanner for Jenkins, SonarScanner for Azure DevOps, SonarQube/SonarCloud GitHub Actions or SonarQube / SonarCloud Bitbucket Pipes. …

Any big differences in the CI logs (particularly SonarCloud analysis) between two runs (before the drop and after)?