Hm, ok well in that case, the work around really doesn't make any sense, because it requires having two alerts set up for the same error?

"When the second alert is triggered by an incorrect latency value, the execution of this procedure will clear the problem. If the latency value is correct, the latency will continue to increase past 30,000 milliseconds. Therefore, the first alert is triggered correctly, and you receive notification of the correct latency value."

I have to admit, I'm a little confused. :ermm: