Hello,

first, awesome illustration. I always wondered how to illustrate such questions but this one was easy to understand and to follow. Will keep this in mind.

Second, in general the for each should run through the collection every time. You could try to clear it before you go into the list query the second time.

Does it change the behaviour?

Kind regards,

Enrico

Hello Enrico

Thanks for your respond and the flowers

I allready implemented this option (delete the actuall collection befor change the state), sadly this does not work.

Hmm, it might be an issue in your environment.

I created a similar workflow like you have:

I query a list that has 4 elements and iterate through the collection, writing the ID of those elements to workflow log.

If I reject the task in State 2, it goes back to State 1 and does everything again.

In workflow log I can see that the collection was iterated twice:

Can you check if you have the latest build version of Nintex Workflow installed? Maybe there was a problem in an older version. You should have version 3.2.1.0 installed but in my version it works too (3.2.0.0).

Kind regards,

Enrico

We have installed the version 3.2.1.0

My log looks like this:

The collection will filled again, but not processed by the "foreach". its goes direct to the state with the flexi task.

But, in your sample it works, so the error is on my side.

do you have any stop condition configured in for each loop, that could cause to skip the loop in second turn?

What might help is exporting the query list action and the loop operation into a second workflow and start that workflow from your state machine, but I wonder why it is not working in the first place.

Yes I have. This could be the reason, I will check this. There's a Yes/No Variable, I should set this variable back to the initial value...

Now it works!

Thanks to Marian Hatala and‌ ‌ for support.

Regards, Simon