cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
pbono
Nintex Newbie

Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

Hello everyone,

I'm having a Problem with Nintex Workflow O365: I have been working on 2 new Workflows for a customer. In all of them, there are "Assign a Task"-Actions. After an item was created and every assignee approved the tasks of the 1st Worflow, the 2nd Workflow starts. When someone rejects the task of the 2nd Workflow, the 1st Workflow restarts automatically, which it shouldn't, because there is a Terminate Workflow Action in the Rejection Branch. 

This issue doesn't happen, when some someone rejects a Task in the 1st workflow.

How do I stop the restarting of the 1st Workflow?

Thanks!

Labels: (2)
0 Kudos
Reply
7 Replies
greenawayr
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

Do you have the first workflow set to start on modification at all?

0 Kudos
Reply
pbono
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

Hi Ryan,

The first workflow is set to start on modification and item creation, the second starts manually.

Should I deactivate the modification setting?

Thanks!

0 Kudos
Reply
greenawayr
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

If your second workflow is doing anything to change the item then it will start the first workflow off again.

Try it to confirm and then we can look at a resolution to your requirement.

0 Kudos
Reply
pbono
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

Thanks, I've deactivated the modification setting and the first workflow stopped restarting.

But now I don't have the possibility to restart the workflow automatically, when I'm modifing the item. And for some reasons the Manual Start of the Workflow doesn't work, because when I'm trying to do that, the site of my customer stops working at 66% with the pop-up message -Waiting for Workflow-.

If you have any solutions to this issue, pelase let me know.

Thank you!

0 Kudos
Reply
greenawayr
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

I think the best approach is to have a rethink about why you need 2 workflows.

If this was on-prem you could use conditions around the "Start on Modified", but I don't think you can do that. The other option on-prem is to run the workflow action under a System Account. Workflows will not start on changes made by System Accounts, I believe. I don't think there is a way of doing this on O365. Maybe someone else knows.

Is there a specific reason for having two workflows? We might be able to suggest a different approach to this.

0 Kudos
Reply
pbono
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

Sorry for the late answer:

We needed 2 WFs because, 1 WF would be too big and complex.

I've realized now that the WF1 always restarted, because we've implemented a 'Set Field In Current Item' Action at the end of the WF1. We need this Action to get ItemID for the 2nd WF. 

Is there a possibility to set a condition in the 2nd Workflow to prevent restarting the first one?

For the Manual Start Workflow Issue, I've already sent a support ticket. 

Thanks for the help!

0 Kudos
Reply
greenawayr
Nintex Newbie

Re: Issue O365:1st Workflow starts automatically after Task rejection of 2nd Worflow

I'm not sure whether the same is possible in o365, but in on-prem, if an item was created or modified by a system account then the workflow would ignore it. Is there a way to create system accounts in O365 and then run the action in an action set under that system account? 

A slightly messier approach could be to put a pause at the beginning of WF1 and then an action in WF2 to terminate WF1. 

However it does look like your best solution might be to merge them into a single workflow and just structure it in a way to make it less confusing.

0 Kudos
Reply