Troubleshoot Playbook Errors
The playbook validator verifies the correctness of the playbook configurations, such as nodes not connected to the workflow, the correctness of dynamic paths configured in the nodes, and more. This section outlines the errors that can occur within the playbook.
When an app instance is not selected for an app action node to interact with the application, the validator displays this error. Select an app instance to resolve this error. For more information about app instances, see Work with App Instances.
The validator verifies and displays this error if nodes are not connected to the playbook workflow. To resolve this error, connect the nodes to the playbook workflow.
The validator checks if the mandatory input fields are provided and displays this error if it is empty. To resolve this error, fill in the mandatory input fields of the node.
Error: Code is required
The validator checks if the custom code is provided and displays this error if the custom code node is empty. To resolve this error, provide custom code in the node. For more information about the custom code node, see Action Nodes.
The validator verifies each dynamic path in the playbook nodes to ensure the node number corresponds to an existing node. If the node number is incorrect or indicates to a node that does not exist, the validator displays this error. Enter a valid node number in the dynamic path to resolve this error. For more information about dynamic paths, see Use Dynamic Paths.
The validator displays this error if the dynamic path used in the node that retrieves data from the memory node consists of any space or special characters other than hyphens and underscores. Remove any spaces or special characters in the dynamic path to resolve this error. For more information about dynamic paths, see Use Dynamic Paths.