Scheduled Workflows Run Multiple Times

  • 26 March 2021
  • 3 replies
  • 366 views
butlerj
Userlevel 5
Badge +19
ISSUE
When a workflow is scheduled, multiple instances of the workflow are run.
ERROR CODE
RESOLUTION
  1. Navigate to Central Administration > Monitoring > Timer Jobs > Review job definitions.
  2. Locate and select Nintex Workflow Scheduler.
  3. If there is more than one Nintex Workflow Scheduler Job running in the farm use the following command to uninstall the jobs: 
    NWAdmin.exe -o UninstallTimerJob -job ScheduledWorkflows -url <WebAppURL>
  4. If there are no Nintex Workflow Scheduler jobs running after performing the above, run the following command to install the job: 
    NWAdmin.exe -o InstallTimerJob -job ScheduledWorkflows -url <WebAppURL>
Note: There should only be one instance of the job in a farm. Do not install the job on each Web App.

 

For more information, see Scheduled workflows and the Nintex Workflow Scheduler timer job.
ADDITIONAL INFORMATION
RELATED LINKS

3 replies

S
Badge +2

I've tried suggested resolution.
It did not help.

Here is our situation.
Workflow, scheduled run once a day.
Schedule settings:

Repeat settings
Repeat every Hours Days Months

Schedule end: Indefinite

It takes about 6 minutes for this workflow to complete.
This workflow does not have any pauses or waiting for anything to change:
only runs SQL query, collects data to build a report and sends emails.

Farm settings
1. Nintex Workflow Scheduler job is defined only once.
2. Nintex Workflow Scheduler: Runs every 5 minutes
3. The job is scheduled to run on 3 WFEs servers.

The scheduled workflow in question  runs twice every time. 
A simple workflow that only logs to history and stops, runs only one most of the time (9 times of 10) but sometimes still runs twice. 


I'm a little bit confused how scheduled jobs on 3 servers are able to synchronize to avoid duplicate runs.
Also, what happens when a scheduled workflow is still running and the next scheduled Nintex Workflow Scheduler job starts.

Any suggestions?
 

butlerj
Userlevel 5
Badge +19

Hi Oleg,

This may be a SP Farm topology issue, or a conflict with how the Workflow Timer Job is trying to execute. I would suggest opening a support ticket and asking one of the engineers to review your farm topology to ensure that everything looks to be configured properly.

S
Badge +2

Thank you. Opened a support ticket.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings