Description of Issue

This article reviews the standard process for configuring the Scheduler Engine

Context

Cause

These are the default Scheduler Engine configurations. They can be customized as needed.

Resolution

Log into the Munis environment with an account that has Scheduler Engine Administrator Permissions
Open Tyler Menu and navigate to System Administration > Scheduler Administration > Scheduler Queue
Select Scheduler > Properties
Review and populate the following variables
1. Engine Default Properties
  1. Initial engine startup mode: Online
  2. Max concurrent jobs: 10
  3. Queue scan delay: 30
  4. Resume after inactivity of: Leave blank
  5. Run command delay: 5
  6. Idle loop delay: 5
  7. For daily maintenance: Remain running, Warn but allow, and 60
  8. Connection loss timeout: 0
  9. Timeout notification address: Leave blank
2. Jobs Default Properties
  1. Jobs expire if not run after: Leave blank
  2. Retain job history: 365
  3. Hold next occurrence if a recurring job expires: Leave unchecked
  4. Hold next occurrence if a recurring job fails: Check
3. Logging Default Properties
  1. Activity logging level: Critical only
  2. Auto-increment log name (add 000-999): Check
4. Scheduling Dialog Default Properties
  1. Enable scheduling dialog: Check
  2. Default start time: 21:00:00
  3. Default job-started notification: Check
  4. Default job-ended notification: Check
  5. Default job-expired notification: Check
  6. 'Background' delay: 00:02:00
Once complete click Accept

Additional Information

Browser not supported