I have been working on a big workflow that has several nested state machines, and has undergone major changes over the last few weeks.
Recently, I began receiving this error: "Error in request review action. The user to assign the task to has resolved as blank text."
The way the workflow works is first it creates a flexi task where the reviewer as the option to choose approve, reject, or need more information. When choosing need more information, the outcome updates the workflow status, then changes state to the need more information state, where there is an action set which logs the created by user, and then requests review from the created by user.
When I am selecting Need More Information, the workflow correctly updates the status then changes states, but immediately errors and gives me the error above. It does not reach the request review action. I know this because it does not reach my log which is placed prior to the action. I'm racking my brain as to why it errors on state change, and why the error produced claims that the error is in the request review action. I have been looking at the visual status of the workflow, provided by nintex, and the workflow does not even make it to my action set.
Any insight would be greatly appreciated, I can have more screenshots ready for help. Thanks!
EDIT: I know that the request review action has someone in the "collect data from" section, because I have hardcoded my email there and it is still errors prior to the action set, while giving the error that the problem lies in the request review action 0.o
Solved! Go to Solution.
- if workflow fails, neither log action need to be effectively written to history list - try to add commit pending changes right after log action
- if workflow really fails on state change then there is a problem somewhere within the state machine branch. state machine change causes all the batched actions are effectively executed, hence error may appear to happen on different action
could you post screenshot of your workflow to get a picture what's going on there?
Thank you for your suggestions, I ended up removing that state machine all together and re-building that section of the workflow and the error is no longer there.