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
5 subscribers
Views
1719 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
We are on Appian 7. (Cloud) We have a process model with several sub-
aksharc
over 10 years ago
We are on Appian 7. (Cloud)
We have a process model with several sub-processes in it. Now, what happen is, for some process, the process would stuck at the Sub-process node. No error, nothing. If I go in that sub-process model in monitor mode, the process seem to be completed till the end node (blue line till the end). But somehow, the flow couldn't come out from the sub-process! I did restart the end node, whole subprocess, and start node in the sub-process. But same result. It won't just go out of the sub-process. Is there any reason why this would be happening?
Let me know if more clarification needed.
Thanks in the advance....
OriginalPostID-112196
OriginalPostID-112196
Discussion posts and replies are publicly visible
0
janakik
over 10 years ago
Does that Sub-Process contain any quick tasks? or any un attended UserInputTask are active?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aksharc
over 10 years ago
The subprocess doesn't contain any user task or quick task. But yea, the status currently shown as unattended (In monitor view)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
janakik
over 10 years ago
If your subprocess contain quicktasks/rule events/message events then terminate the process by configuring the end node of your subprocess.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joel671
over 10 years ago
So this looks like you need a terminate event instead of an end event. So if there is more than one flow in the sub process and they reach the end event the sub process does not complete but waits for a terminate event. I have seen this happen when a node fails inside a Sub process and someone restarts it without killing the node which fails. To fix it firstly all you will need to do is open the running process in edit mode and change the end event to a terminate, save and close. Then open the map in monitor mode and restart the end event and this will then complete the process and continue the flow in the parent map.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aksharc
over 10 years ago
Thanks Janakik for the input.
And, Joel671, your fix worked. Thanks a bunch!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel