Trigger Flaps Ok/Problem During Complete Down State

[low10sws6]

ITEM:
Interval -120sec

icmppingloss
icmppingsec
icmpping[,6,20,100]

Trigger

{ICMP Template:icmpping[,6,20,100].last(240)}=0 &
{ICMP Template:icmppingloss.count(240,100)}=2 &
{ICMP Template:icmppingsec.last(240)}=0

this trigger works as far if all checks match

ping = 0
PacketLoss = 100 twice within 240 sec
latency = 0

the trigger triggers an alarm to give me a true down state
but after so many minutes the trigger status goes OK then back to Problem after another couple minutes

while the item check has shown this check to have been down the entire time.

my guess is that after every 240 secs the trigger rechecks showing an OK status until after all checks complete again to show problem

I'm trying to create a trigger that verifies the problem has been down for a period of time of 240 sec in making sure that the problem is a complete down state rather then a connection flapping

for a flapping connection i have this check which works great

{ICMP Template:icmpping[,6,20,100].last(0)}=0 &
{ICMP Template:icmppingloss.last(0)}<100 &
{ICMP Template:icmppingsec.last(0)}#0

i'm i doing something wrong or is this bug