Inconsistent Storm Watch Behavior

[trmmcd]

Yesterday we had our first Storm Watch activation as the result of a tornado warning. However, it didn’t activate until about 20 minutes into the warning. In the meantime, nearby downed trees knocked out power nearby. The Storm Watch mode ended exactly at the end of the warning interval which is what I expected. While I was glad to see it activate, the late start limited its usefulness.

Today - we just had exactly the same storm scenario - a significant storm with another tornado warning. There was no activation of Storm Watch.

This leaves me baffled as to what alert condition initiates Storm Watch. It seems as though there must be human intervention and the same practices are not consistently followed.

 

[commasign]

Yeah, feels like some part time worker managing the system. We had a wildfire preemptive power shutdown thing going on a few weeks ago in Northern California. Storm watch didn’t turn on until after the threat had passed. And it stayed on for several days more.

 

[boaterva]

Huh. I thought it was a lot more automated than that. We had it activated for thunderstorm warnings and I doubt they are manually tracking every tstorm warning countrywide. May have just been a glitch.

 

[boaterva]

Yeah, feels like some part time worker managing the system. We had a wildfire preemptive power shutdown thing going on a few weeks ago in Northern California. Storm watch didn’t turn on until after the threat had passed. And it stayed on for several days more.

This may be the case where it needs to be done manually and is a problem of someone being aware. Wonder if calling in would help in these cases?

 

[ez123]

Storm watch briefly activated in San Diego yesterday afternoon, but there was no storm, not even close.