Skip to main content

Starting and Stopping the Scheduler

Scheduler State

To view the scheduler state
  1. Open the Farm menu group of the navigation panel.
  2. Select the Access Servers node.
  3. Select an access server from the available list to view its details. The states for the System Scheduler and Tenant Scheduler are displayed. Refer to System Scheduler Status and Tenant Scheduler Status for information about scheduler operational states.

System Scheduler Status

StatusBehaviour
RUNNING
  • If previous state was STOPPED, the database will be reloaded prior to normal operation.
  • Dashboard updates normally
  • Other system scheduler internal functions operating as normal
SUSPENDED
  • No Dashboard updates
STOPPED
  • No Dashboard updates

Tenant Scheduler Status

StatusBehavior
RUNNING
  • Scheduled group requests will be submitted to JDE and run as normal.
SUSPENDED
  • No scheduled group requests will be submitted to JDE.
  • Currently active jobs will continue to completion.
  • Queued jobs will be run.
  • If the scheduler currently has zero threads, a minimum thread count (2) will be assigned.
STOPPED
  • No scheduled group requests will be submitted to JDE.
  • Currently active jobs will be terminated.
  • Queued jobs will be deleted.
DISABLED
  • Scheduler thread count is set to zero, meaning no jobs can be run.
  • No scheduled group requests will be submitted to JDE.
  • Currently active jobs will be terminated.
  • Queued jobs will be deleted.

Controlling the Tenant Scheduler

To change the scheduler state
  1. Open the Farm menu group of the navigation panel.
  2. Select the Access Servers node.
  3. Select an access server from the available list to view its details.
  4. Use the Tenant Scheduler Control buttons to select the required state (RUNNING, SUSPENDED, STOPPED or DISABLED).

    The Tenant Scheduler cannot be started if the Scheduler Thread Count is 0.


Suspending the Tenant Scheduler

When the scheduler is suspended, no new jobs will be submitted. If a scheduled group's submission time passes, the execution is skipped and the next execution time is calculated based on the schedule.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.