Description

Scheduled jobs from Studio or jobs created by the Winshuttle Workflow Autorun plugin remain in the Managed Scheduled Jobs queue in a "Not Started" status.

Applies To

User Governance 11.x, SAPIS 11.x

Solution

The scheduled job queue maintains a list of jobs to run.

The Winshuttle Central Autorun SharePoint timer job is responsible for picking up the jobs from the list of scheduled jobs and sending them to Winshuttle SAPIS for processing. This job runs every 5 minutes. The first time the job runs, it will check how many scheduled jobs can be started based on how many jobs are current in-process. By default, a maximum of five jobs can be processing concurrently. The Winshuttle Central Autorun SharePoint timer job will set any scheduled jobs that can be started to an "In-Queue" status.

The next time the Winshuttle Central Autorun SharePoint timer job runs, it will pick up all "In-Queue" jobs and send them to SAPIS to be posted.

When a job remains in the "Not Started" state, this indicates the Winshuttle Central Autorun SharePoint timer job is not running.

Troubleshooting steps:

1. Ensure the SharePoint Timer Service is started

SharePoint utilizes the SharePoint Timer Service to perform timer job actions, this service should be in a running state. Ensure the service is running and if it is running, perform a restart on the service. This action must be done on every SharePoint web front end server.

2. Verify the Central Timer Jobs feature is activated

In SharePoint Central Administration,

1. Click on Manage Web Applications
2. Click on the web application hosting Winshuttle
3. Click on Features in the ribbon.
4. Ensure both Central Timer and Central Resource features are activated.

3. Verify the Timer Job is successful

While in SharePoint Central Administration,

1. Click on Monitoring
2. Click on Review Job Definitions
3. Find the Winshuttle Central Job
4. Ensure it reports as Successful for every web front end

If there is a failure or the last run time shows "NA", deactivate the Central Timer Jobs feature from Step 2 and re-activate it. This can interrupt any users on the site, but should only take a few minutes for re-activation.

Scheduled Job Clog

In Winshuttle Central Administration, under Application Settings the Query section contains a value for how many scheduled jobs are allowed to be processed at a time, as a protection against heavy system use.

If the Winshuttle Worker service or Timer Jobs are interrupted, scheduled jobs can remain indefinitely stuck in a processing status adding to the total count. If too many reach one of these stuck states, the concurrent job count will reach the total allowed and no further jobs can be processed.

Check the Managed Scheduled Job to view which jobs remain in a state between Not Started and Completed for longer than expected. If these jobs are stuck, they need to be removed (and rescheduled if the data is needed).