Flow restoration exception

[Cantor, Scott]

That's the normal exception the back button raises if the flow never completed. Once the flow completes, the execution number (the e1, etc.) is removed, and the back button raises the other one. A submit wouldn't cause it without a user doing other unexplainable (in the "why would anybody do it?" sense) things before the submit. Anything that perturbs the browser history relative to the conversation's state on the server kills the webflow code one way or the other with one of the exceptions thrown.

I guess the way to think of it is when the e1 is wrong you get the other one, when the s1 is wrong, you get this one.
 
-- Scott