lordmilko

@Silex In regards to your question, if you have a sensor then the best way to get the device is to do `Get-Device -Id $sensor.ParentId`

Hi @bajayb4u, `-ErrorAction` only applies to non-terminating exceptions (i.e. emitted `ErrorRecord` objects). To ignore an exception you need to wrap the relevant code in a `try`/`catch` block ```powershell try {...

Hi all, Please be advised I have been able to reproduce this issue and have released a new pre-release build of PrtgAPI which should hopefully include a fix for this...

Hi @bajayb4u, You should not be doing ```powershell $cpuchannel = Get-Channel -Sensor $cpusensor ``` If `$cpusensor` contains multiple objects you'll get the error you got above. This is an error...

Hi @JustinGrote, You are exactly right, this is the issue. I am already aware of the limitations of executing large requests, and have already taken steps to work around them...

Hi @Silex, This behavior is intentional, as when I was implementing this I found there was no way to have a parameter set that allows specifying an `-Id` and `-Period`...

Hi @cyberoner1, After reproducing the error can you please provide the output of `$error[0].Exception.StackTrace`

Thanks @cyberoner1, Can you also do the following: First do ```powershell Set-PrtgClient -LogLevel Response ``` then invite `Get-SensorHistory` again, specifying the `-Verbose` parameter ```powershell get-sensor -tag tableau -type snmptraffic,snmpdiskfree,snmpcpu,ping -status...

Hi @cyberoner1, Just following up on this, are you able to advise?

Hi @squintfox, Thanks for providing these logs. I have pushed a commit which I believe should contain a fix for this issue. Are you able to test PrtgAPI 0.9.18-preview.5 by...