Another BSC3 PT132 gauge glitch caused a VACSTAT false alarm at 00:28:26 this morning. I captured the MEDM (attached) and restarted the service at 07:02.

As in previous PT132 glitches, it is the detaP channel which triggered, just exceeding its trip value of 1.0e-08 Torr

Code is being worked on to mitigate this issue.