Replies: 2 comments 2 replies
-
Thanks for reporting this, @d0finley ! Currently testing this, should be included in the next release |
Beta Was this translation helpful? Give feedback.
1 reply
-
1.2.4 has just been released. Let me know if the problem still occurs |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
First off, thank you for putting this utility together!
In my testing, I've found a limitation in cases where you have a flow that has several parallel actions directly off of the trigger. In those cases, only the first parallel action branch is added to the graph output.
Reviewing the "runAfter" case in the FlowParser.parseActions method, it looks like there is an assumption that you will only ever have a single node that has no runAfter definition, but that's not always true.
I'm sure you could write something more elegant, but I thought one simple way to handle this would be to create a static root node, and then you could start the entire action graph there, for example:
Beta Was this translation helpful? Give feedback.
All reactions