Resubmitting Failed Workflows

Very often we get workflows to get failed for different reasons, there are many workflows but here I am considering the failed Requisition Approval workflow and steps to resubmit of the same.

Ex: Requisition Approval workflow(REQAPPRV) failed with error:
      Error Name  WFENG_NOTIFICATION_PERFORMER 
      Error Message  XXXX: Activity 'REQAPPRV/XXXXX' has no performer. 

>> Check, workflow status monitor to see the failed or error-ed activity and reason.
    >> To view the workflow diagram
          Go to the Purchasing Responsibility > Requisitions > Requisition Summary
           >> Search with requisition number
           >> 'Tools' > 'View Approval through Workflow'
           >> check the failed activity, and view diagram or click on the 'error' it will show you the error details.
           >> Note down the 'Item Key' of the failed workflow.
   OR check the wf_notifications table to get the item key
           select item_key
            from wf_notifications
          where subject like '%<Requisition Number>%'
 

Now Resubmission Process

Navigation
   >> Either 'Workflow Administrator' responsibility > 'Status Monitor'
        OR
             'System Administrator' responsibility > Workflow > Administrator Workflow > 'Status Monitor'

1> Search the workflow with 'Type Internal Name' and 'Item Key', you got in the above step.
2> Select the workflow and click on 'Activity History'
3> Select the failed activity and click on 'Update Attributes'
   >> Update the missing attributes, in this case update 'Preparer User name' and 'Preparer Display Name' with the output of the below query.

      select b.full_name
        from po_requisition_headers_all prha
               ,per_people_x ppx
        where prha.segment1 = <Requisition_number>
           and prha.preparer_id = ppx.person_id

   >> 'Apply' the changes and go back to 'Monitor Activities History'

4> Select the error-ed Activity and click on 'Rewind'
     > Accept the rewind confirmation
     > Check the workflow status again.
5> It should do the job else check for errors and take appropriate actions accordingly.