Is there a limit to how many transiitions a state ...
# suiteflow
b
Is there a limit to how many transiitions a state can have? I have a transition that NS doensn't seem to detect because when I check the transaction(JE) log, it is the only transition not listed as being considered as if the transition didn't exist at all.
k
Try deleting it and recreating it
b
Are you talking about the specific transition or the entire workflow? And what is the basis of this suggestion?
k
The transition
Because I've tried stuff like that in the past and it has worked
Shouldn't work. Shouldn't make a difference, but I've literally seen it work
b
Alright I'll try it out. Any insight on why this happens? And is there a limit or a recommended number of transitions a state should have?
k
No idea why it happens. Normally frustrates me to no end because it's my last resort
How many transitions are you working with?
I have had issues in the past with mutually exclusive transition criteria not working quite right
I.e. Using the same field as criteria for 3 transitions
b
From the first state it has 7 possible transitions. The first six gets logged fine in the transaction workflow log. The 7th I actually added late and haven't tested a lot but it's very sinilar to the other transitions. They all have user role conditions.
The only thing that bugs me is it isn't considered at all in the workflow log as if it's invisible. But I'll try recreating it tom hope it works
r
when looking at the workflow logs did you check the "show rejected actions"
b
yes that's what I mean by it's invisible because it's not even part of the rejected actions
I tried recreating it @KevinJ of Kansas but it still didn't work. However, I got it to work by changing the order of the transitions inside the first state. Seems like since I added the 7th transition late, it was at the bottom of the transition list. Does this mean that there is actually an order to how SuiteFlow checks the transitions? Before I edited it the Approved transition(6th) was before my 7th transition which I'm thinking is the reason the 7th wasn't showing up in the log because it already recognized the 6th state as True.
k
Yeah, once a transition is true it stops evaluating other transitions