How to Troubleshoot Node Issues

This passage will walk you through how to troubleshoot node issues from the perspective of incomplete workflow configuration, unavailable signature, and child workflow-related errors.

Demonstration

When saving and enabling the workflow, you may receive error alerts for workflow nodes.

Incomplete Workflow Configuration

Here are 4 causes that will cause incomplete workflow configuration. You can find solutions for each.

Cause 1 Approver/Field Permissions Not Set

When setting workflow nodes, you need to set the corresponding approver to handle the workflow. When the node approver or the field permission is not set, you will receive an error message when enabling the workflow, and the workflow will not be saved.

Solution

Set the corresponding node approver and field permissions and then enable the workflow again.

Note:

This issue could be happening on any node except the end node.

Cause 2 Node That is Not Connected

When there is an isolated workflow node or the node does not form a closed loop, the workflow will not work properly. If you click Enable, it will prompt you to delete the node.

Solution

If the node is unnecessary, then you can select the node and delete it directly to remove the node and then enable it.

If the node is needed, you forget to set the connectors with other nodes, or the connection is not closed. Then you need to set the correct node connector to form a closed loop before enabling the workflow.

Cause 3 Plugin Not Configured

When you enable a workflow with Plugin Node before configuring the Plugin Node, the following error will be reported and the workflow will not be saved.

Solution

Select the Plugin Node, and Click Plugin Configuration under Node Properties. Then enable the workflow after configuration. For details, see Plugin Node.

Cause 4 Sequential Approval Rule Not Configured

When you set Sequential Approval to Node Approver under Node Properties and enable the workflow before configuring the sequential approval rule, the following error will be reported and the workflow will not be saved.

Solution

Select the Approval node. Then go to Node Properties > Basic > Node Approver and click Configure Rule. Enable the workflow after the configuration of sequential approval rule. For details, see Sequential Approval.

Signature Not Available

Signature is a premium feature. If the signature has been enabled before, the feature will no longer be available after the end of the experience period and the expiration of the version. Then, when you save the workflow, it will indicate that the signature is not available, and you need to modify the settings.

Solution

Disable the Signature in the Approval Comment.

Note:

If you need to use Signature, you can contact our Sales Team to upgrade the plan.

Child Workflow-Related Errors

Here are 3 causes that will cause child workflow-related errors.

Cause 1 Incorrect Configuration for Child Workflow Form or Initiator

You add a child workflow node in the form, but the child workflow form and initiator are not configured correctly.

Solution

You need to configure the child workflow form for the child workflow node and set the initiator for the child workflow.

Cause 2 More Than Three Layers of Nesting or Looped Settings

1. Loop settings: A (parent workflow) > B > C > A (child workflow). A is the parent workflow and indirectly constitutes the child workflow. You can constitute a workflow form configuration into a loop under the rule.

2. More than Three Layers of nesting: A > B > C > D. That is counting three layers. A is the parent workflow of B, B is the parent workflow of C, and C is the parent workflow of D. If you add a child workflow in the D workflow, it will be more than three layers.

Cause 3 Transferring Failed Data at Certain Node to the Admin

The asynchronous Child Workflow nodes are connected in the shape of a ring with or without the Plugin Node.

In this case, the workflow fails to proceed to the next node.

Solution

You need to modify the workflow by adjusting the connectors to avoid the case that the asynchronous Child Workflow nodes are connected in the shape of a ring with or without the Plugin Node.

I have finished reading. 🏆

👉I can't wait to TROUBLESHOOT NODE ISSUES.

👉I need more HELP in Discord Forum.