For the second time tonight, I've lost lock because ISC_LOCK reached some state and decided it was time for a break. Each time, locking was finally going okay, no obvious issues, then Guardian reaches some state that I want it to wait at, and it then refuses to move on. No amount of, loading, pausing, execing, requesting higher states then switching to manual and going back to the current state will get it to move on. Only INITing, which then causes ISC_LOCK to go to DOWN.
The most recent "freeze" may have been due to ISS second loop engagement issues. I don't remember what state I was in when I lost lock last time, but I just had to go through manual engagement of the ISS second loop, and I was at first worried I was stuck again. The first freeze was on DC Readout, so it definitely wasn't an ISS issue.
Could we get some kind of error message if the second loop fails to engage after a couple minutes? I only figured this out because the log said: "2015-11-02T10:51:13.61264 ISC_LOCK new target: ENGAGE_ISS_2ND_LOOP", and I remembered that the ISS 2nd loop had issues.
INIT should be safe, if you go to Manual, select INIT, then select the state that you had been at, *then* go back to Auto. If you're in Auto when you are in INIT, it will go to Down.