I'm still not sure what happened, but the SUS_CHARGE Guardian had a connection error for the H1:SUS-ITMX_L3_DRIVEALIGN_L2L filter bank, but it looks like it should have been a GAIN. Looks like this happened last week as well - alog71899. Before Camilla came in and pointed that out to me, I first tried stopping the node and then re-exec'ing it to create new epics connections, but this didn't work. I took the node to DOWN and then tried the injections again, but then stopped it a bit too early. I also fixed some tabs to spaces that might also have been creating some guardian confusion.

Fixed now and we ran it past the error point then brought it to DOWN for maintenance.