cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

nintex workflow state machine not moving to Previous State when the Task was rejected

nintex workflow state machine not moving to Previous State when the Task was rejected . I have a workflow with different states and flexi tasks .When the task is approved my workflow is working fine with different States. But when the Task rejected my workflow is not moving to the intial  State. Please find the attached workflow.

 

Issue reported :we have a workflow set up for documents. it first goes to the doc specialist. once approved, it goes to the document reviewer. if the reviewer approves, it goes to the document approver, and then after approved, the workflow is complete. the problem we're having is if the reviewer or approver rejects. we have the state machine set to return to the requester, but instead it just loops back to the reviewer or approver.

0 Kudos
Reply
4 Replies
Automation Master
Automation Master

Re: nintex workflow state machine not moving to Previous State when the Task was rejected

If you could post a picture of your workflow in the designer and the configurations around your Change States I can check the basics. Unfortunately I do not have on-prem available to me currently.

0 Kudos
Reply
mlauer
Nintex Newbie

Re: nintex workflow state machine not moving to Previous State when the Task was rejected

Workflow Analyzer from Aaron Labiosa shows in this Flexi Taks default branches without a Change State action. Check configuration of this Flexi Task actions (see also Do you really know the Flexi task? from   ).

0 Kudos
Reply
mlauer
Nintex Newbie

Re: nintex workflow state machine not moving to Previous State when the Task was rejected

You need no on-prem version, You can use Workflow Analyzer from Aaron Labiosa.

0 Kudos
Reply
tbeduneau
Nintex Newbie

Re: nintex workflow state machine not moving to Previous State when the Task was rejected

I saw this warning yesterday with Analyzer, but can't figure how it could be the cause of the issue...

0 Kudos
Reply