Previous Topic

Next Topic

Book Contents

Book Index

How Schedules Work

MOVEit Automation checks for new tasks to run once a minute. Each time a check occurs, the scheduler scans all tasks to see which ones are eligible to run this minute. A task is eligible to run if ANY of its schedules lists the current minute as a valid time to run. The same task is not run multiple times in a minute, even if more than one of its schedules matches the current minute.

If the Maximum Running Tasks is set to 0, all eligible tasks are started simultaneously. Otherwise, the scheduler starts as many eligible tasks as it can without exceeding that setting. The other tasks are queued, and are run after currently-running tasks complete. Each task runs in its own thread..

A task is not run if a previous copy of the task is still running. Missed runs are run the next time that the scheduler runs and sees that another copy of the task is not running. However, no more than one missed run will be made up. For example, if a task is scheduled to be run at 9:00, 9:05, 9:10, 9:15, and 9:20, and the 9:00 task takes 16.5 minutes to run, then the 9:05 and 9:10 runs of the task will be skipped. At 9:17, the scheduler will run the 9:15 task two minutes late.

The scheduler does not run tasks that were scheduled to run prior to the time that MOVEit Automation was started. In the example above, if MOVEit Automation is started at 9:17, it does not run the task until 9:20, skipping the 9:00, 9:05, 9:10, and 9:15 runs.

Schedules and Event-Driven Tasks

Schedules also control when event-driven tasks are run. Events that arrive for an task are ignored unless they arrive during the scheduled time window. Missed files are handled by an automatic task run performed automatically when the task enters its next scheduled window.

For example,

To schedule tasks on a periodic and event-driven basis, use the option Run even if notifications are enabled for the host.

To schedule a task to ignore file events, set it up to run once at specific times.

Schedules and Failover

At startup, and when a secondary failover node becomes primary, MOVEit Automation runs all event-driven tasks whose schedule covers the current date and time.