I have a sensor with 3 channels. The channel that is my concern is a Lookup based channel. I have defined the sensor with the following:

- Setting, Scanning Interval="30 minutes" and If a Sensor Query Fails="Set sensor to warning for 2 intervals, then set to down"

- Notification Triggers = "When sensor state is Down for at least 600 seconds(10 mins), perform >>HTTP call<<"

What I expect to happen:

• 1. PRTG detects that the channel has value Error -> sensor is not yet set to Down (as per "Scanning Interval" section definition)
• 2. in 30 min the second check happens, channel still has value Error -> sensor status still does not become Down (as per "Scanning Interval" definition)
• 3. after another 30 mins channel has again value Error -> as the 2 scanning intervals which mean = 60 minutes have passed, sensor status becomes Down in PRTG
• 4. if in another 10 mins(defined in Notification Triggers) sensor status is still Down the HTTP call is executed

> so once PRTG said the channel value is Error, sensor had its status set to Down after ~ 60 mins and in a total of **70 minutes PRTG makes the the alarming HTTP call

What actually happens:

• 1. PRTG detects that the channel has value Error -> sensor status become Down
• 2. in 11 minutes the HTTP call is executed Could you please explain why this happens the way it does instead of what I expect as per my understanding of the PRTG manual?

lookup-channel notification-trigger scanning-interval