If your workflow contains errors, you may not be able to publish your workflow. To help you troubleshoot any issues, the Workflow Designer highlights any issues in the canvas. You can click on the error message to go directly to the affected node.
There are two key reasons why you may not be able to publish your workflow or why your workflow may not work:
Missing connections
Node configuration
Missing connections
If you forget to connect a node to another node, the Workflow Designer highlights any missing connections in red when you try to publish the workflow.
Node configuration
If you incorrectly configure a node or it is missing required information, a warning message is displayed. If you hover over the node, a tooltip message indicates the reason why the node isn‘t correctly configured.
Depending on the type of node, the error message varies. These are the errors you may encounter:
Invalid path
This error requires you to specify an action. If this is shown, check the node and make sure that you have specified an action (e.g. if it‘s a draft node, select submit, recall, etc.)
Disconnected workflow
This error can appear in different circumstances. In general, the validation algorithm checks the validity of the whole workflow and if it finds that one node cannot be converted into a proper workflow, it flags that path as invalid. This causes the rest of the nodes connected to a specific workflow node to be invalid too.
Activity node error
This error requires you to perform an action on the activity node, i.e. fix properties or missing information on the node.
Condition node error
This error requires you to perform an action on the condition node, i.e. fix properties or missing information on the node.
Missing node exit
This error means that you are currently missing an exit path from a specific node.
Duplicate path action
This means that for a certain node you had two identical outgoing actions. For example, for the draft node, you have two outgoing Submit actions. Because they are duplicated, the Workflow Designer flags that you fix it.
Missing start node
This happens because you don‘t have a starting workflow node. If this happens, start from scratch again by using one of the templates.
Missing mandatory node exit
This happens because the node is currently missing an exit connection. A typical case is that you forgot to specify an outgoing path from a certain condition node.
💡 Tip
When you get an error, try to fix the issues sequentially and publish again to check again if the issue persists. Often issues “cascade”, meaning that the first issue also causes the other errors. Hence, you should check the error messages step-by-step and slowly iterate.