About Resubmitting Process Instances and Process Steps

You can use the resubmit feature in Monitor to repair and re-execute process instances that have failed, or to re-execute completed process instances. Note that only webMethods-executed processes can be resubmitted.

A key component of the resubmit feature is the ability to edit the pipeline associated with a step within the process instance prior to the resubmit operation. This is useful for modifying pipeline data that could be causing the failure.

The Process Instance page contains two buttons for resubmitting process instances, Resubmit Closest and Resubmit Earliest. These buttons are active only when applicable conditions exist. Note that the specific behavior of the system in response to a process resubmit request depends on which button you click and on the state of the process, step, and model, as explained in the following para

Note:
The resubmit buttons and their associated table check boxes are displayed only when an Integration Server (IS) is available.

You can resubmit one or more process instances from the Navigate > Applications > Monitoring > Business > Process Instances page. In most cases, you will need to use the Search feature to find processes with the appropriate status within the desired time frame. The resubmitted process begins executing at the appropriate step, depending on the factors described in the following paragraphs and the resubmit button that you choose.

A process with a “Completed” status may be resubmitted based on whether the process has steps that are resubmit-enabled, as follows:

Process contains a resubmit-enabled step may be resubmitted using either button. In each case, the process instance execution is re-initiated.

Process does not contain a resubmit-enabled step cannot be resubmitted. Clicking either button has no effect.

Process contains a resubmit-enabled step but the step was not executed during the original run cannot be resubmitted. Clicking either button has no effect.

Processes with a “Suspended” status resumes from the point at which it was suspended if you click either the Resubmit Closest or Resubmit Earliest button. When you resubmit a step of a suspended process, webMethods Monitor first resumes the process and then resubmits the suspended process from the requested step.

Process instances with a “Failed” status may be resubmitted, with the following order of precedence:

The Resubmit Closest button does the following based upon whether the failed step is resubmit-enabled:

Failed step is resubmit-enabled, the process instance resumes executing at the failed step.

Failed step is not resubmit-enabled, the process instance begins executing the closest step to the failed step that is resubmit-enabled that has been executed previously.

Failed steps are not resubmit-enabled and there are no steps that have been executed previously, no action is taken.

The Resubmit Earliest button begins executing at the first step that is resubmit-enabled, in the line of processing for that instance. If no steps meet the requirements for process instance re-execution, no action is taken.

You resubmit a process instance by resubmitting a step within that process instance. The resubmittal procedure varies depending on the status of the steps within the process:

A process instance with a “Completed” status may be resubmitted from any step in the instance, provided you have first enabled the step for resubmission before the process instance began executing.

A process instance with a “Failed” status may be resubmitted from any process instance step that has failed. A failed step is automatically enabled for resubmission, and the pipeline at the point of failure is automatically logged by the Process Engine and made available to Monitor. No manual configuration is needed. Process instances with Failed (Escalated) status cannot be resubmitted as the parent process is no longer waiting for a response.