Restart Failed Workflow Instance

When an error stops a workflow instance, the error is recorded in the Workflow Logs and the workflow instance is marked Unsuccessful with a red X under Status. Errors can occur for several reasons, such as an improper format, incomplete data, or a dropped connection from a power outage. Some workflows needs a jump start, while others need to be corrected before they can be restarted.

Note: Most restart functions are available ONLY to Cloudsnap Support and Customer System Administrators. 

To find Failed Workflow Instances

You can find a failed workflow instance through the Workflow Logs, which lists all workflows instances with the most recent first, or the Daily Digest, which lists the workflow instance that ran the previous day.

From the Workflow Log

1. In the Cloudsnap platform, click Integration Management>Workflow Logs.
2. On the Workflow INSTANCES page,
   • Scroll through the workflow instances
   • Or, search by Workflow (Name) or Status (Failed in this case), within a date range.
3. Once you find the correct workflow, click the down arrow on the far right to view the information about the workflow error. See the example that highlights the failure markers and the actions that can be taken.

    

From the Daily Digest

1. In the Cloudsnap platform, click Resources>Daily Digest.
2. On the Daily Digest page, choose the Workflow (Name), Date, and Status (Unsuccessful).
3. Once you find the correct workflow, click the down arrow on the far right to view the information about the workflow error. See the example that highlights the failure markers and the actions that can be taken.
   

Types of Restarts

Note: To determine which method to use to restart a failed workflow instance, see Resume or Relaunch?

Restart the workflow instance by one of these methods, which are in the Action drop-down list.

• Resume restarts at the step where the workflow failed. Use this option when a connector fails or the agent is not responding. 
• Mark as Successful only when the step failure has been determined to be an incorrect error; for example, when a workflow test causes an error.  
• Relaunch restarts the workflow at the initial trigger. Use it after one or more major repairs to the general workflow or the data in the workflow instance.
  Warning: Relaunching can send duplicate records to the destination application, especially if the failure occurred several steps into the workflow. To minimize duplications, use Relaunch only as a last measure. 
  For example, an invoice from the source app that does not contain a Purchase Order (PO) number stops the workflow instance because the ERP requires that all Invoices have PO numbers. 
  First, update the invoice in the source application then relaunch the workflow instance. If you cannot repair the workflow instances, contact Cloudsnap Customer Support for assistance.
• Auto-Resume sets the number of times to retry a failed workflow instance before it is marked failed and affects the subsequent steps in the workflow instance. The function is set up on the Edit page for workflows. Set up Auto-Resume on the Edit Workflow Details. See Auto-resume workflow.