Exec checks failing - but script logging shows success #136

Hi,

I am running the latest version of checkup on a Windows Server 2019 VM.
I have it configured to do many basic HTTP, TLS and port checks, all of which work perfectly with almost no false positives.

However, I wanted some more, in depth checks for a few things, so I have two PowerShell scripts running via exec.
Here is my config for launching them:

    "type": "exec",
    "name": "SanCheck",
    "command": "powershell",
    "arguments": ["-ExecutionPolicy", "Bypass", "-File", "c:\\checkup\\santest.ps1"],
    "Threshold_RTT": 60000000000000
    },
    {
    "type": "exec",
    "name": "Cluster Status",
    "command": "powershell",
    "arguments": ["-ExecutionPolicy", "Bypass", "-File", "c:\\checkup\\cluster-Online.ps1"],
    "Threshold_RTT": 6000000000000
    },
    {
    "type": "exec",
    "name": "Printer Webcam 1",
    "command": "curl",
    "arguments": ["http://192.168.1.6:8080/?action=snapshot_1 --output temp.jpg --max-time 2"]
    },

Now. The last check, the webcam one, never give me a false positives. it takes less than a second to complete.

The first two are more complex and take between 2 and 9 seconds to complete their tasks and return a result. As you can see I have added a huge threshold to these as I do not want them ever timing out. However, quite frequently I get alerted that these exec checks are failing.

I enabled logging on these scripts to see if they really were failing or not, and they return good results every time, bar a few when it seem like the script was forcibly closed for some reason.

Nothing I can do seems to stop these from giving me lots of false positives every day.
I will attach the PowerShell scripts for you to take a look at, but they are nothing crazy.

Powershell scripts.zip

Im fairly sure this is a bug cutting the execution off, but if this is a config issue on my part would greatly appreciate some help!