About the CSPSystem, I had some troubles to connect when I used the superuser from VSC and the webgateway had the CSPSystem user configured, It solved when I changed the user to superuser.

Probably you are right and is not necessary to change the CSPSystem (my current configuration it's using CSPSystem and works fine) it just was pure chance.

You can use $ZF(-100) command to execute operative system commands (here an example), with that command you can look for the process that is locking the superserver.

Well, I highly recommend to you to not use the same instance of Health Connect for TEST, DEV and PRODUCTION, even more, I recommend to you to deploy each environmnent in different servers.

It won't be the first time that a code un DEV has a infinite loop creating heavy globals that use all the space in the disk.