lordmilko

> GetObjectPropertiesRaw does not return the full set of NotificationAction properties if the user calling it only has read access That is correct. As noted on the [wiki](https://github.com/lordmilko/PrtgAPI/wiki/Property-Manipulation#get): > Note...

Ah of course; `GetObjectPropertiesRaw` functions slightly differently to `GetSensorProperties`, et al. This is still the correct behavior (although I'm surprised it even returned anything at all). The usability of `GetObjectPropertiesRaw`...

Did this issue only start happening recently? Or did you only start using PrtgAPI and/or this feature recently and so this has always occurred?

I haven't been able to reproduce this issue myself, however are you able to advise * Whether upgrading to PRTG 22.1.75 resolves the issue? * Whether the sensor is actually...

@bajayb4u, I have no idea what the issue is; when trying to repro this you should be running one liner commands to narrow down what the source of the issue...

@carlbeechvuw, What sort of sensors are you trying to add? Can you provide the output of specifying `-Verbose` to the `Add-Sensor` cmdlet when it crashes (please omit the server, username...

Can you see if you can replicate this issue with HTTP, WMI Service or Advanced EXE/Script sensors? I would like to see whether you can reproduce the issue when using...

Please see my post above and advise what occurs if you test using raw HTTP/WMI Service/EXE Script Advanced sensors using raw + non-raw types

PrtgAPI should be able to handle any scenario regardless of load; the common scenario is that API requests time out (as opposed to returning random error codes). PrtgAPI has special...

Based on the reports made in this thread it sounds to me as if HTTP status code 556 can indeed be safely ignored as objects are actually created properly, however...