I have not been able to reproduce this behavior with version 3.17 which was released yesterday, could you please update and check whether the issue still exists?
If it does, would it be possible for you to share the contents of your VSCode user settings for the following properties:
I’ve also found that when sonarlint identifies that the folder can be bound by itself, through the message “Do you want to bind folder ‘folder-name’ to project ‘org-key_folder-name’ of SonarQube server ‘’?” and you click “Configure Binding”, it sets up settings.json correctly.
I was indeed able to reproduce this behavior as soon as there are several connections defined and one has no connectionId. I created a ticket to address this.
As a workaround, you can either add a connectionId to the connection that doesn’t have one (and use it in the folder settings), or manually add "connectionId": "<default>" to the sonarlint.connectedMode.project property in the appropriate folder settings.