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
3 replies
Subscribers
9 subscribers
Views
1960 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
XOP Gate --> Is there a limit to the number of parallel instances coming to t
aneeshv
over 11 years ago
XOP Gate --> Is there a limit to the number of parallel instances coming to the XOR Gate over Multiple Instances because we executed more than 50,000 Instances at the same time parallely and some of them are now waiting on the XOR Gate for no reason.
Everything else seems to be good from the Process Development Presepictive (Using this tool)...
OriginalPostID-70663
OriginalPostID-70663
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Yes, that's the expected behavior, the OR-XOR gateway waits for the other incoming flow to be activated. That's why this is not a best practice and instead you need to use a script task before (even if it's an empty script task) to join all the incoming flows and direct a single one to OR-XOR.
This is explained in our documentation
forum.appian.com/.../OR_Node:
"When multiple flows enter an OR node, the Gateway node pauses after the first instance token passes through – until all other incoming flows arrive. Work around this issue by placing an empty Script Task node between the incoming flows and the Gateway node. "
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Yes, that's the expected behavior, the OR-XOR gateway waits for the other incoming flow to be activated. That's why this is not a best practice and instead you need to use a script task before (even if it's an empty script task) to join all the incoming flows and direct a single one to OR-XOR.
This is explained in our documentation
forum.appian.com/.../OR_Node:
"When multiple flows enter an OR node, the Gateway node pauses after the first instance token passes through – until all other incoming flows arrive. Work around this issue by placing an empty Script Task node between the incoming flows and the Gateway node. "
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data