I've got a "Assing A Task" action with "Escalate or auto-complete" option set to "Escalate to person or group":
Any reminders are off.
Unfortunately this doesn't work (no emails, no tasks on Workflow Task List). Any ideas?
Solved! Go to Solution.
Hi Maciej Flis
Bashya Rajan A
Thanks Bashya for the link. I've checked once again settings and all are OK.
Please see the screenshot below:
and this is simple test workflow with loop and one task action:
Have you set the "fx" on "Created" to be "datetime"? Also, as Milan wrote - try to log your "Created" datetime and check if the condition you set (Created+2 minutes) can be met. Moreover - I guess this can work as some sort of a timerjob. Usually those are triggered every 5 minutes, but since this is O365, this timerjob cannot be provisioned to the tenant, but is possibly done as some sort of Remote Event Receiver that listens to the list. Now, as it is RER, it has it's lags, so either the 2 minutes timespan is too short to be caught or there is an issue with the time perception (timezones?).
So first - try to log the time, second - try to set the condition for ex. 1 hour.
And you can also get familiar with this post: https://community.nintex.com/community/build-your-own/blog/2015/12/01/how-to-configure-escalate-and-... - maybe it will put some light on your issue?
From support team:
Thank you for your patience whilst I investigated.
Due to the nature of the issue, I wanted to test multiple iterations and configurations to ensure the behavior was as expected.
If the Workflow Task action does not 'Wait for Task to be completed' then the Auto Complete function will not work as the action is considered complete. There is no workaround for this and I would recommend that you perhaps look at utilizing a different workflow design in order to achieve the task process that you require.
One possible workaround would be to create parallel actions to generate the tasks and await their completion however this could result in a very large workflow.
I thought about it. I mean - I was nearly sure it is caused by the fact, that the process does not wait for the task to be completed and the task itself is considered completed so the logic behind does not work. I experienced that as I was testing out your workflow in your second question: https://community.nintex.com/message/61699-re-issue-with-tasks-in-start-a-task-process
If you think this explanation is sufficient and that you found answers for your question, please don't forget to mark one of them as "correct".