I've seen exception classes split into recoverable and non-recoverable. The former clean up as they propagate and move the application to an initial known state

I've seen exception classes split into recoverable and non-recoverable. The former clean up as they propagate and move the application to an initial known state in a state machine. This works fine. I think the worst bug was an exception thrown from the initial state which lead to an infinite loop.