I have a somehow critical workflow "Determine technical owners".
This workflow:
Technically, this is a:
Everything worked well during the test. In production, however, I get errors here, the workflow always stops after 5-6 minutes (no matter where it stands).
Until then he works correctly. Do you have any idea where to look here?
My first research showed that Nintex can only start 15 workflows at times and the rest are then "put on hold"?
For me, the following questions arise:
• do you know the problem?
o Do you see a way to divide up the mass of the accelerated workflows via Nintex?
o If yes, are they customizable?
I thank you.
FYI, I have added a counter in the workflow, which is incremented by +1 for each list workflow to be checked.
Each time the counter reaches 100 (100, 200, 300 ...), the workflow is paused for five minutes.
That seems to work now, but maybe there is a more elegant solution?Cheers
mai-kel
Hi Michael,
I've usually found that, when looping lots of item, workflow errors at some point and only solution is to put a pause in it like you've already done..maybe you can find the best point for your environment where to put the pause (after 100/150/200) because I've found that this may change based on the SharePoint Environment, so everytime I have to find the best settings for my scenario..
Giacomo
Hi Giacomo,
OK, thanks, I already thought something like this. I'll keep the question open for some days, maybe there is somebody else with a good idea.
If not, I 'll mark your answer as correct.
Thanks again and best regards
mai-kel