The last analysis has failed. If it keeps on failing after several attempts, please contact us and provide the following failing analysis ID: 3ac32da3-eab4-4b0e-be0f-9e4db02d2666.
Welcome to the Community! Thanks for providing the analysis ID.
Your analysis ran for about 38 minutes, processed a large number of files, and then failed abruptly without a specific error, this pattern usually points to a resource issue (likely
memory) partway through the scan, rather than a problem with a specific file. The project being scanned is a large codebase which puts more strain on the analysis than smaller projects.
A couple of options to move forward:
Reduce what gets scanned: add a .sonarcloud.properties file at your repo root excluding legacy/vendored JS that doesn’t need analysis using the sonar.exclusions=xxx parameter. This can meaningfully cut down scan time and resource use., see: Additional analysis configuration
Switch to CI-based analysis: since Autoscan’s resource allocation isn’t configurable, running the scan via your own CI (e.g., GitHub Actions) gives you more control, you can increase the scanner’s memory allocation, which is generally the better long-term fit for a codebase this size.