Skip to main content
Nintex Community Menu Bar

There is a workflow which is stuck in status [Running] and does not complete.
Within the main workflow, there is a child-workflow which needs to be compled before continuing.

 

The child-workflow has already finished and is complete.

However, the main workflow is still running since few days.

19302i127DB616A271567B.png

 

Is there a way to 'push' the main workflow to continue ?
Why did this happen anyway? Is this a Timer Service problem?

I am not familiar checking logs about TimerService etc. not sure how to.
Would the workflow automatically continue to work if the Timer Service is restarted?
Besides there is a Recycle Time Service running everyday; would that not restart it?

Importantly, would restarting the Timer Service have a chain-reaction on other instances? Would it cause any problems or stop 1000's of workflows? What is it's negative impact?

 

Cheers

A few questions

1. Does the main workflow *always* get stuck when ran or does it only *sometimes* get stuck? 

2. Does the secondary (child) workflow actually get to the end state (End Workflow) or does it just complete its work? The reason I ask this is because if it has a state-machine or something similar, it could be technically doing all of the work it's supposed to be doing, but just not actually finishing creating an issue such as this.



 



 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings