Previous Topic

Next Topic

Book Contents

Book Index

Task Schedule

A task can have more than one schedule. To run automatically, a task must have a minimum of one schedule. Tasks with or without schedules can be run manually by the operator.

In a task with more than one schedule, each schedule runs independently of the other schedules.

Schedule Field Descriptions

Add/Edit Schedule Field

Description

Days tab

 

Week

Month

Week and Month selections - The schedule runs on all of the days you select.

Example: In Week, Monday and Thursday are selected; and in Month, 10 and 21 are selected. The schedule runs on every Monday and Thursday every week, and on the 10th and 21st of every month.

Custom

Adds a date list to the schedule.

Date lists must have been previously created and added to MOVEit Automation to be included in the drop-down list. For more information, see Date Lists.

Select the date list and specify how to reference it:

  • Include: Run the tasks on the dates specified by the date list
  • Exclude: Do not run the task on any date that is specified in the date list. This behavior overrules (takes precedence over) any other days or dates in the schedule.

Note: Do not use a date list and an overnight interval (for example, start time 10 pm and end time 3 am) in the same schedule. Instead, use two schedules in the task, one for the date list and the other for the overnight interval. Each schedule runs independently of the other schedule.

Times tab

 

Start time

 

Scheduled start time.

If Repeat is not selected, the task runs at the time you specify, on the days of the week and month that you selected on the Days tab.

If no days are specified on the Days tab, the schedule runs once at the first occurrence of the start time you specify.

If the source host has file notifications enabled, polling occurs during the times specified by the schedule, at intervals defined by the polling interval. If files are available, the task runs.

Interval

End time

Available if Repeat is selected.

Specify the repeat interval and an end time.

If the end time falls at the repeat interval, the task runs at the end time. For example, with a 2 pm start time, 3 pm end time, and repeat interval of 30 minutes, the task runs at 2 pm, 2:30 pm, and 3 pm.

Note: Do not use a date list and an overnight interval (for example, start time 10 pm and end time 3 am) in the same schedule. Instead, use two schedules in the task, one for the date list and the other for the overnight interval. Each schedule runs independently of the other schedule.

Another time

Specify a start time to run the task, and an optional repeat interval and end time.

Details appear on a separate row. The schedule runs on all the times and intervals that are defined on all the rows.

Options tab

 

Repeat only until first success

Available if Repeat is selected.

This option is ignored if all sources have file notifications enabled.

Runs the task at the intervals specified, as long as no previous run in the schedule has successfully downloaded and processed files.

After a task successfully retrieves and processes one file, all further runs in the schedule are suppressed until the next day.

If you know that only one batch of files will appear within a given time range, this feature can be useful in reducing the load on remote servers and on MOVEit Automation.

Log failure if no files found during scheduled run

During the last run of a task during the schedule, the run fails if no runs during that schedule have succeeded in downloading and processing a minimum of one file.

Example:

You expect a customer to place a file on a server every Friday between 1 am and 5 am. You schedule a task to run every 10 minutes during that time. If no file has appeared by the last run in that period, the run is logged as failed.

Note: If you select this option, it is recommended that you designate a Next Action/Failure setting (for traditional tasks) or Conditional step (for advanced tasks).

Run even if notifications are enabled for the host

Available if the host associated with the source has File Notifications enabled.

The task is run according to this schedule even if all associated source hosts have file notifications enabled.

See also: