Hi there,
I'm trying to get details about a typical error that I constantly seeing on a process.
A little background: This process is suppose to read rows from the uploaded spreadsheet, based on row validation it has to complete two sets of DB updates. In current configuration these uploads are done when the valid rows are passed through a start process smart service. Since we have to update two different tables we have created a parallel flow after AND gate to complete the same. But the problem arises when one of the node completes and hits the end node and the other node waiting of the sub-process to complete. Please check the screenshot attached.
Consider to share the reason for this error and suggest the possible methods to avoid this.
Thanks,
Vishnu Devalla
Discussion posts and replies are publicly visible
Place a AND gateway before the end node, and the process will continue only when both paths are completed.
Add a Join gateway after the parallel branches. This ensures both branches complete before the process continues.Review Appian documentation on parallel flows: https://docs.appian.com/suite/help/24.1/AND_Node.html
What is the error you observe?
This is expected behavior of your design. As the end node is triggered before completion of your other nodes, that would end the process irrespective of other nodes status. As others suggested you need to add a AND gateway before the end node. But what is the error? I haven't experienced what it does to a start process node.
Yes Stefan, I've observed this error on Production
Hey, Chaitanya.
I've a concern what if it is the behavior of node and not the design. Like upon placing the AND gate to ensure the two nodes complete only then it could reach the END node, there is a possibility that it could be a behavior of the node rather than mere reaching the end node causing the parsing issue.
May i know are you using terminate event anywhere?
No, we are not using terminate event on any sub or main process
I have just tried using a similar design and I don't see an issue though. what is it the error that you see? Can you share more details on your process design and flow?
You may be creating one or 2 instances at each start process smart service link. Consider we have a file with 900 rows and each of these rows has to be stored on external DB, this will create 900 instances at each start process node and then you might get this issue