Best practices for setting up schedules

For optimal performance and ease of maintenance, keep these guidelines in mind.

• Because scheduled runs are executed on the system where the client product is installed, consider the scaling capabilities of the client system. Stagger runs or use throttling to tune the system.
• When possible, schedule heavy jobs during low system load times.
• Avoid overlapping runs, which cause run failures.
  • Use caution if you use the same object in multiple schedules. For example, if you use flowchart F1 in three schedules, these schedule definitions could cause a run to be started before a previous run completes, causing run failure.
  • If a flowchart run is initiated manually or by an external script, a subsequent attempt to run the flowchart by any means fails with a lock error if the previous run has not completed.
• The scheduler creates large quantities of data. If you observe performance issues with the scheduler, consider removing schedule definitions that you no longer need.
  Important: Removing a schedule definition also removes its associated run history from the database.