Hi ​@jpacheco,

If you have no conditions, does the workflow move on?
If you only have one condition, does the workflow move on?
Is there any reason you are using this action instead of running all the tasks in parallel, as the workflow will not move until all parallel paths have completed?
In the screenshot, we can only see a glimpse of what the workflow is doing, so it is hard to determine what else may be pausing the workflow.

​@SimonMuntz

Thanks, so in response to your questions…

If you have no conditions, does the workflow move on? Yes
If you only have one condition, does the workflow move on? No, tried that... Its the same response. I tried checking to see if just one of the fields were populated (at least) but it seems to act like my hidden field doesn’t get populated, when it does and so it just waits.
Is there any reason you are using this action instead of running all the tasks in parallel, as the workflow will not move until all parallel paths have completed? All tasks are running in parallel. So after each task is approved, the form gets updated with approver info. I have hidden fields on my form that get updated once each task is approved. The hidden fields collect the outcome of each task that was actioned. Once the WF gets to the ‘wait for event’ action, it checks those fields that were updated by the workflow and if they all show to approve, then it moves on. 

All hidden fields start out empty in my form and then when the tasks are actioned, they get updated with the approval outcome. Whether that be rejected or approve, anyhow it applies that outcome to the hidden fields.

Do you have to actually modify the form and click submit in order for the wait for event action to work?

This is basically the layout.

Hi ​@jpacheco,

Thanks for providing the additional information.
Based on your answers, there may be an issue with the condition as the workflow continues without one.

For the Wait for event in list item action for SharePoint Online, Yes, the list item must be updated before the action is triggered. The action is waiting for an update. If there is no update to the item, it will wait until there is.

​@SimonMuntz ,
 

Is there something in particular you have to do when using the parallel action? It seems it behaves different…. The conditions I’m using in fact update cause when I go back into the form, I see the values in the fields. Just weird that it continues to stall...

I did come across someone else’s issue on here (link below) and I tried it but it works on and off for me… I apply a completion condition and set it boolean to NO and then I add variables at the end of each ‘assign a task’ and set the boolean to YES. Again, it worked yesterday but today its stalling on the ‘wait for event’ action. I went back in and removed the variable in the complete condition section and the WF moved passed the ‘wait for event’ action and completed!

I’m confused to what is going on…. could you help?

Thanks!

Hi ​@jpacheco,

It’s always hard to diagnose these things on a forum like this.
The only thing I can suggest is to log the variables before evaluating them to ensure that you are evaluating what you expect.

The events page may also give you a clue as to what is happening with the event trigger.
https://help.nintex.com/en-US/nwc/Content/Dashboard/Events.htm

​@SimonMuntz ,

I appreciate your time. I guess I’ll have to reach out to technical support for more assistance. Thank you.