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
6 replies
Subscribers
4 subscribers
Views
2823 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
I have an AND gateway that is only executing one path. If I go into monitor the
joshuar975
over 8 years ago
I have an AND gateway that is only executing one path. If I go into monitor the process, I can manually start the node the AND gateway is not flowing into, and it works and runs fine.
Originally I had an OR gateway, that was also executing only one path, even when the conditions were set as true and true so I took the longer route of flowing an XOR into an AND, but this does not work either even when the AND gets executed.
I'm on 7.11
OriginalPostID-202765
OriginalPostID-202765
Discussion posts and replies are publicly visible
0
shailendras593
over 8 years ago
Hi Joshua,
What it looks from the screenshot is that the lower path (that is executed) is executing faster than the upper path or vice versa. So, when either of the two paths reaches first to the terminate node, it is killing all the active nodes(since it is terminate node and not the end node) i.e the active 'AND gate'. In other words, the whole process is getting terminated , even before the second path from the AND gate begins to execute. Therefore killing the active AND gate node.
To check this, you can make the terminate node an end node and see what happens. I think both the paths from the AND gate will execute.
Further, to resolve this, you can place a COMPLEX gate before your sub-process node and route both the paths from the AND gate to this COMPLEX node, and configure the COMPLEX node in such a way that it should move ahead only when both the incoming flows have reached.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mark Talbot
Appian Employee
over 8 years ago
Do you get the same behavior if you remove the terminate?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joshuar975
over 8 years ago
Removing the terminate node works. Thank you.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mark Talbot
Appian Employee
over 8 years ago
It's still a good practice to have a terminate at the end of each process model. Work to address the logic in your node so that it functions with the terminate. You will likely need a complex node at the end of the model to collect your process flows.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joshuar975
over 8 years ago
Yes I managed a fix while keeping the terminate node.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
marky
over 8 years ago
If you are not using an AND gate to join multiple paths, but instead to separate multiple paths, then you should use a blank script task node instead. It would be worth it studying a little more on what gates are used for. In addition, its a good idea to label the script task as "split", and make sure your path flow lines are not over top of each other. When dragging a path flow, you can connect them to any 4 directions of the target node.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel