This scenario includes cases where a user is editing a work item and the node upon which the user has a session goes down before the work item can be submitted.
Without Session Persistence
User experience: A nontransparent failover. When the work item edit form is submitted, the user is logged off and returned to the login page.
Recovery steps: Upon resubmitting login credentials, the user's work item is marked completed and the workflow can resume from that point. The workflow should be picked up by the new mode for execution from the point where the user's manual action is marked completed.
With Session Persistence
User experience: When the work item edit form is submitted, the user sees the effect of his submission—for example, either the next form in the custom workflow if there is one, or a success message.
Recovery steps: No user action needed.
Other Scenario Examples
An end user is filling out a form associated with a manual action in a custom workflow, for example requesting access to specific resources. Before the user can submit the request, the node the user has a session on dies.
An administrator has logged in to Identity Manager and has opened up an approval request for editing. Before the request can be submitted, the node the administrator has a session on fails.