Problems when resuming a BP on certain type of errors

In some cases, that can be reproduced, when a Business Process is running and a database outage occurs, this BPs goes into a halted status with "Rollback Transaction Error" and "Commit Transaction Error" errors.

This situation appears to create some dysfunctions on B2B:

First dysfunction:
When trying to take care of this Halted WF, some options are given: Resume or terminate.
Even if RESUME is chosen, B2B will restart the BP from the beginning.
What causes some integrity on the business and financial impact.

Second Dysfunction: When doing the resume action, wrong documents (and Instance Data) are used.

On the seek to understand what's happening and solving this situation (There's the need to resume and not restart the wf), a sql was developed that solves that problem.

With the SQL command below, it is possible to convert the BP state from Halted to Interrupted_Man, enabling successful resume action.

UPDATE
   WORKFLOW_CONTEXT WC
SET
   SERVICE_NAME = 'BUSINESS_PROCESS_MARK',
   DOC_ID = NULL,
   BASIC_STATUS = 450,
   ADV_STATUS = 'Service Interrupted',
   CONTENT = NULL,
   WFE_STATUS = 403,
   WFE_STATUS_RPT = NULL,
   SVC_PARM_VER = 0,
   LIFE_SPAN = -1,
   PERSISTENCE_LEVEL = 3,
   ARCHIVE_FLAG = -1,
   ARCHIVE_DATE = NULL,
   DEADLINE = NULL,
   CONTRACT_ID = NULL,
   EVENT_LEVEL = 0
WHERE
   WORKFLOW_ID = <BP ID>
   AND STEP_ID = <STEP ID - STEP IN ERROR>

Note: The behavior is observed in BPs that DO NOT use Transaction Services.

This leads us to believe that the exception handling of the errors reported above were not handled correctly.

And if the resume is not possible on this situation, B2B should not give this option and/or show a message confirming the restart.

Case for reference: TS017555191.