VS Code Terminal Not Detecting Apex Issues Despite Correct SonarQube Configuration

Hello Team,

I’m experiencing an issue where the VS Code integrated terminal is not detecting or displaying Apex errors, even though my SonarQube server connection and configuration appear to be correct. The terminal successfully displays issues for other front-end technologies such as HTML, CSS, and JavaScript, but Apex-specific issues are not appearing at all.

Below is all the required environment information:


Environment Details

SonarQube Version

  • Enterprise Edition — Standard Experience

  • Version: v2025.6.1 (Build 117629)

  • Status: ACTIVE

SonarScanner / Build Details

    • SonarQube for IDEVS Code Extension : version: 4.45.0
  • Salesforce Extension Pack : version: 66.1.1


What I Am Trying to Achieve

I want the VS Code terminal to detect, analyze, and display Apex code issues the same way it currently does for HTML, CSS, and JavaScript. Apex issues are not being recognized despite what appears to be a successful connection to the SonarQube server.


What I Have Tried So Far

  • Verified that the SonarQube server connection is active and reachable.

  • Confirmed that the project configuration in VS Code is correctly set up.

  • Checked that the Apex plugin is installed and active.

  • Ensured that scans for other languages work as expected.

  • Restarted VS Code and reloaded the workspace.

  • Validated that file types and paths are correctly included in the analysis.

Despite these steps, Apex errors still do not appear in the integrated terminal.


Request

Could you please help identify what might be preventing Apex-related issues from being detected or displayed in the VS Code terminal? Any guidance or troubleshooting steps would be greatly appreciated.

Thank you! :folded_hands:

Hi,

Welcome to the community and thanks for this report!

Could you provide a verbose log from IDE startup through to where you’re (not) seeing an issue?

 
Thx,
Ann