Right now, if a GW alert occurs in a run marked Bad or with filters offline, it will get stuck inside of the check_events_after function (L152). There should be a check that if there are no events found, this raises an error rather than getting stuck in a loop.
Right now, if a GW alert occurs in a run marked Bad or with filters offline, it will get stuck inside of the
check_events_afterfunction (L152). There should be a check that if there are no events found, this raises an error rather than getting stuck in a loop.