When saving or enabling a workflow, you may receive error messages for individual workflow nodes if the workflow is not configured correctly. This article introduces common node issues, explains what causes them, and provides the corresponding solutions.

When configuring a workflow node, you need to set the appropriate Node Approver and Field Permissions so that the workflow can be processed properly. If the Node Approver or Field Permissions have not been configured, an error message will appear when you enable the workflow, and the workflow will not be saved.

Select the affected node and go to Node Properties. Configure the Node Approver and Field Permissions, and then enable the workflow again.

If a workflow contains an isolated node, or if the nodes are not connected to form a complete workflow path, data cannot proceed through the workflow properly.

In this case, an error message will appear when you enable the workflow.

1. If the node is unnecessary, select the node and delete it. Then enable the workflow again.

2. If the node is required but has not been properly connected to other nodes, add or correct the necessary connections so that the workflow forms a complete path, and then enable the workflow again.

If a Plugin Node has been added to the workflow but has not been configured, an error message will appear when you enable the workflow, and the workflow will not be saved.

Select the Plugin Node. Under Node Properties, click Plugin Configuration and complete the required settings.

If Node Approver is set to Sequential Approval but the sequential approval rule has not been configured, an error message will appear when you enable the workflow, and the workflow will not be saved.

Select the node and go to Node Properties > Node Approver. Click Configure Rule and complete the Sequential Approval settings.For details, see Sequential Approval.

Signature is a paid feature. If Signature was previously enabled but your trial period has ended or your current plan no longer includes the feature, Signature will no longer be available. When you save the workflow, an error message indicating that Signature is unavailable will appear. You will need to update the relevant node settings.

Go to Node Properties > Actions > Notes and disable Signature.

A Child Workflow node has been added to the workflow, but the child workflow form or workflow initiator has not been configured, or the configuration is invalid.

Configure the workflow form to be used by the Child Workflow node, and set the Child Workflow Initiator.

For example: A (parent workflow) → B → C → A (child workflow)

Workflow A is initially the parent workflow, but it eventually becomes its own child workflow indirectly through B and C. This creates a circular child workflow configuration.

2) More than three levels of child workflow nesting

For example: A → B → C → D

This represents three levels of nesting: A is the parent workflow of B. B is the parent workflow of C. C is the parent workflow of D. If another Child Workflow is added to workflow D, the configuration exceeds the supported three levels of nesting.

An asynchronous Child Workflow node has been added to the workflow, but one of the following circular configurations exists: Asynchronous Child Workflow nodes form a loop or an asynchronous Child Workflow node and a Plugin Node form a loop.

As a result, the workflow encounters an error and cannot proceed to the next node.

Modify the workflow configuration and adjust the node connections to eliminate the loop. Make sure that asynchronous Child Workflow nodes do not form a circular path with other asynchronous Child Workflow nodes or Plugin Nodes.

I have finished reading. 🏆

👉I can't wait to VIEW ADMIN ACTIVITY.

👉I need more HELP in Discord Forum.