Right now we track when an automatic client reset begins, and if we start another automatic client reset before ending the first, we raise an error that looks like A fatal error occured during client reset: 'A previous '<reset mode>' mode reset from <date> did not succeed, giving up on '<reset mode>' mode to prevent a cycle'. We should also track the reason the first client reset began so that we can see in the second aborted client reset what error caused us to begin the cycle in the first place.