Llyr Posted February 29 Share Posted February 29 I'm using parallel processing to manage the addition of customers to multiple AD groups depending on their selection. All the ITOM actions take place but the timeline update doesn't happen and the process is just suspending on the end parallel process node and not moving forward. where am i going wrong? This is how my process looks: and it just stays like that Link to comment Share on other sites More sharing options...
Steve Giller Posted February 29 Share Posted February 29 Is it just one of the Timeline updates for the triggered ITOM actions, or all of them? If one, there's possibly an issue with the connected ITOM action, if all of them it may be that the process does not "see" the ITOM action finishing, so is not able to progress. Link to comment Share on other sites More sharing options...
Llyr Posted February 29 Author Share Posted February 29 So, i get the timeline update for the first one but none of the others. Also i have tried removing all the timeline node update and just have it doing the ITOM work and i get the same issue, so it could be what you mentioned @Steve Giller that the process doesnt see the itom actions finishing. Any suggestion to test that theory? Link to comment Share on other sites More sharing options...
Steve Giller Posted February 29 Share Posted February 29 I would suggest running them in sequence without using Parallel Processing at all. If that works then they may simply not be compatible with Parallel Processing. I don't have a domain to test against, so if the above doesn't work, or you have an overriding need to run them in parallel post back here and one of the Developers will be able to respond. 1 Link to comment Share on other sites More sharing options...
Llyr Posted March 1 Author Share Posted March 1 Have ran the processes in sequence and it all works. Thanks 1 Link to comment Share on other sites More sharing options...
SamS Posted March 1 Share Posted March 1 @Llyr, Obvious problem: you are ending the parallel processing incorrectly: to END parallel processing you need to use the "Finish Parallel Processing"-node. This is visually different: ORANGE not GREEN. Link to comment Share on other sites More sharing options...
Steve Giller Posted March 1 Share Posted March 1 [Insert smh gif here] Link to comment Share on other sites More sharing options...
Llyr Posted March 1 Author Share Posted March 1 Hi, I did have the finish node in: it looked green when i was looking at it from the Managing Executed Workflow section to see why it was not moving forward. I wish it was that simple of a mistake Link to comment Share on other sites More sharing options...
Steve Giller Posted March 1 Share Posted March 1 Ah - of course - the current node is green in a live workflow regardless of type. I feel better now. 1 Link to comment Share on other sites More sharing options...
SamS Posted March 1 Share Posted March 1 @Llyr grumble - I thought is was that simple. Am I correct in assuming that the "result" nodes are all just updating Custom fields? OR are they doing something different? Specifically, they shouldn't be "Pending"-nodes. Could you please send Support your workflow and we can have a look. Link to comment Share on other sites More sharing options...
Llyr Posted March 1 Author Share Posted March 1 All the results node should do is just update the timeline with the results of the automation. I will log a support ticket now about the issue and send them the workflow. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now