VSCode problems list does not include compilation errors

Description

VSCode Java polugin is not showing the compilation problems before i compile the project.
Not sure, but maybe is because i have the "autobuild" disabled.

The problem is that if i turn on the autobuild option it interferes with Maven and makes VSCode totally unusable for java because every time I launch a maven command, every step Maven do, in the background, the plugin is continually autobuilding and breaking Maven working.

So i disabled the autobuild feature. But now i can't see any compilation error without compiling it manually.
Maybe I'm wrong and it has nothing to do with autobuild.

The question would be, how can I see compilation errors without having to constantly compile. Something similar to what Eclipse does.

Environment

Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: C:\libs\apache-maven-3.8.2
Java version: 17, vendor: Oracle Corporation, runtime: C:\libs\jdk-17
Default locale: es_ES, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
VSCODE: 1.62.2 3a6960b964327f0e3882ce18fcebd07ed191b316 x64
Java extension pack: v0.18.6

Keine Quelldatei und kein Test werden genannt. Beginne damit, das Verhalten bei fehlenden Problemen in VSCode bei deaktiviertem autobuild zu reproduzieren, und vergleiche es dann mit aktiviertem autobuild und einem Maven-Befehl unter dem gemeldeten Windows-, Java-17- und extension-Setup; abgeschlossen ist es, wenn Kompilierungsfehler ohne manuelle Kompilierung erscheinen und Maven-Befehle nicht beeinträchtigt werden.