Problems of Failed Workflow Submission

Introduction

When you fail to submit a workflow, the admin should quickly identify the problem involved to ensure a smooth flow. The followings are the summary of the problems we may meet when submitting a workflow, whereby the admin can quickly solve the problems based on actual conditions.

Summary of Problems

Next Node Rule Not Applicable

1. Why it happens

If you have added a condition in a workflow and the submitted record does not meet the condition, you cannot submit the workflow form. Edit the form to meet the condition or modify the condition before submitting it.

2. How to solve

If you fail to submit a workflow due to Next Node Rule not applicable, find and solve the problem in the following ways:

a. Identifying the record submitted unsuccessfully

Tick Manage Data, identify the record submitted unsuccessfully, and view the record.

For example, Application No. is 00048. Click the Filter button, add a condition, and enter the number to check the record.

b. Checking Updates

In Updates, view the cause of the failure and the node where you fail to submit the workflow.

c. Checking Chart

In Chart, view the version number, the current node, and the next node.

d. Checking the version number

Select the same workflow version in the workflow.

For example, as the version number in Chart is V25, click the V25 version.

e. Checking the flow line and the condition

As the failure happens on the Start node, the next node rule is not applicable, and the next node is Administration Department, we should check the flow line between Start and Administration Department.

For example, the workflow will flow to the next node when the applicant is Alan. Check whether the submitted record meets the condition.

If the applicant is not Alan, you will fail to submit the workflow form.

Could Not Find the Approver for the Next Node

1. Why it happens

If the system fails to find the approver you select from Auto-assign, it will show Couldn’t find the approver for the next node. Then the administrator should select another approver.

For example, if A is the head of a department and you have not set him as the head in Contacts, the system will not find the approver for the next node.

2. How to solve

If you fail to submit a workflow due to Couldn’t find the approver for the next code, find and solve the problem in the following ways:

a. Identifying the record submitted unsuccessfully

Tick Data Management, identify the record submitted unsuccessfully, and check it.

For example, Application No. is 00048. Click the Filter button, add a condition, and input the number to check the record.

b. Checking Updates

In Updates, view the cause of the failure and the node where you fail to submit the workflow.

c. Checking Chart

In Chart, view the version number, the current node, and the next node.

d. Checking the version number

Select the matched workflow version.

For example, as the version number in Chart is V35, tick the V35 version.

e. Checking the approver setting

As the failure happens on the Start node, the system cannot find the approver for the next node, and the next node is Administration Department, you should set Administration Department. That is, you have not set a member as Level 4 Department Head in Contacts.

The followings are the ways to set the approver:

f. Inactive approver

If the approver on a node is inactive, you should reset an approver, click Handover in Inactive Members, and set Handover in batches.

Does Not Match Child Workflow Node Input Conditions

1. Why it happens

In any case of the following circumstances, you fail to submit a child workflow.

2. How to Resolve

a. In the first circumstance, enable the child workflow.

b. In the second, re-transfer the form into a child workflow and add conditions for Parent Workflow and Child Workflow.

c. If the child workflow is deleted, ask the admin to restore it. If it is not granted the Cross-App permission, set the Cross-App form in Cross-App.

d. In the fourth, click Handover in Inactive Members to take over the child workflow.

Loops Existing in the Multi-Branch Workflow

Problem Description

If a loop exists in a multi-branch workflow, it will disrupt the normal flow because data will flow among the nodes in the loop in circulation.

This problem occurs in two common cases including "Multiple Branches Extending From One Node " and "Multiple Dependent Loops," distinguished from the status of the last finished node, as shown in the workflow Chart.

1. Multiple Branches Extending From One Node

Multiple Branches on One Node means that there are multiple branches extending from the last finished node. The nodes to which multiple branches are about to flow are connected in a loop.

For example, in the following chart, if the Task Node is the last node where data is submitted, there will be two branches extending from it. The two branches are activated, namely, the branch from Task Node to Node in a Loop 1 and the branch from Task Node to Node in a Loop 2. However, nodes in the loop are not activated successfully, which indicates that Node in a Loop 1 and Node in a Loop 2 are connected in a loop.

The data will flow into nodes in the loop at the same time. You can find that connectors of Node in a Loop 1 and Node in a Loop 2 form a closed loop.

2. Multiple Dependent Loops

In this case, no activated connector extends from the last finished node, and there are finished nodes involved in another loop.

For example, the Inventory Approval node is the last node where data is submitted, and the connector extending from it is not activated.

The Inventory Approval Node is involved in Loop 2 of Purchase Application > Finance Approval > Inventory Approval > Purchase Application, and the Purchase Application and Finance Approval nodes are involved in Loop 1 of Purchase Application > Finance Approval > Purchase Application at the same time.

Solutions

When the failed submission is caused by loops in the multi-branch workflow, you can deal with that according to the following ways.

1. Modifying Proceeding Conditions

Note:

This solution is applicable to the first case "Multiple Branches Extending From One Node."

Select one of the connectors that extends to nodes in the loop. Modify the proceeding condition to avoid the situation that data flows to multiple nodes in a loop at the same time.

2. Replacing the Connector with the Workflow Returning Feature

Note:

This solution is applicable to both cases, including "Multiple Branches Extending From One Node " and "Multiple Dependent Loops."

Delete the connector that causes the loop. Then enable the workflow returning feature to displace the connector.