Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
7 subscribers
Views
2341 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Manually restarted a task and when process completed does not return to parent p
briank538
over 8 years ago
Manually restarted a task and when process completed does not return to parent process.
How do I get it to continue back to the parent process? I have many PV's that I capture as output in the parent process, so I can not just start the next node in the parent process.
OriginalPostID-209969
OriginalPostID-209969
Discussion posts and replies are publicly visible
0
Tim
Certified Lead Developer
over 8 years ago
Edit the sub-process and add a terminate event to the end node. Then go back to the monitor view and start the end event again. This should return back up to the parent process.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
briank538
over 8 years ago
Ok. Let me see if I understand this.
Monitoring/editing an in-flight process, adding a terminate node for a process that has been restarted will allow it continue back to the parent calling process. I'm slightly confused. Doesn't terminate event kill (end) the entire process including the parent chains? Unless my understanding is wrong, why the different treatment of terminate event?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 8 years ago
The termintae event will only end the current process and any child sub-processes that have been started synchronously. It will not have any affect on the parent process that started it.
I think you can also cancel the previous instance of the node (that I assume error'd) before restarting it, this should also allow the chain to return back to the parent.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sparshs
over 8 years ago
This error i have encountered before and for this you have to kill previous instances of the node. This is just a checkbox you have to select in Others tab.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rama
over 8 years ago
Hi brian,
Above two points are the valid and possible solutions to the issue encountered for you.
When a node crashed in a sub-process, which does not have a terminate event, even after fixing the issue and the flow reached end event the instance will still be active as the node which got crashed will be with the status "Unattended".
And so this leads to the main process to wait infinite time for the sub-process to get terminated.
With any of the above implementations, it gets resolved. But the solution - checking the property “Delete previously completed/cancelled instances” in “Other” tab - is most suitable when you implement a flow that includes more than one node to undergo a loop (not MNI).
So, please try placing a terminate event in the process model that you have configured in the sub-process mode and publish it so that you can avoid these kind of crashes in future.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel