Common scheduling fields

The table below describes common fields found on many input dialogs used for scheduling.

Name

Type a name for the scheduled task (up to 50 characters).

Description

Type a description of the scheduled task (up to 200 characters).

Load balance limiter n Second(s)

(For a task for a group of devices.) Type the value to be used by the scheduler to distribute the load caused by the scheduled task on a group. The value specifies the time period, in seconds, in which the scheduled task activity can be spread (starting from the task start time). For example, a group that has six devices and a load balance limiter of 180 seconds (three minutes) will result in a scheduled task for which the devices will report for this scheduled task at evenly distributed intervals within that three-minute period. The start time of the tasks for the devices will be approximately 30 seconds (180/6) apart.


Best Practice for the load balance limiter

To avoid worst-case loading of the Enterprise server, use the biggest load balance limiter you can in order to spread the load over a large period of time. For file transfers and Questra SoftwareDirector operations, be sure to consider the download time, as this increases the duration of the transaction and hence the number of concurrent downloads. Remember that devices can be added to a group after a scheduled task is created. In this scenario, the least busy time frame is selected, but the time window may not be optimal for the new number of devices. A good rule of thumb: The longer the operation and/or the more devices, the bigger the load balance limiter.

Type

Select the task's type (Enterprise task or Device task).

Watchdog Delay x Seconds

(For Device task only.) Type the number of seconds for the watchdog delay time. This delay specifies the window of time around the task's start and fire times (based on the selected recurrence, below) that allows for clock drift, network congestion, or any other reason for a delay in the device's reporting. As long as the device reports within the start and fire times, plus or minus the watchdog delay, no "Asset task watchdog" alarm will be triggered. (For information on this and other types of alarms, see Alerts and Alarms - An Overview.)


Best Practice for the watchdog delay

Because device clocks are rarely synchronized with a reliable time source, they tend to drift, sometimes significantly, over time. To account for this, use a generous watchdog delay that is very likely to cover this clock drift and other delays that may cause the scheduled task report time to deviate from the start and fire times. For a typical scenario, a watchdog delay of 3600 seconds (1 hour) would be reasonable.

Recurrence

Enter the task's frequency. For Per minute, Hourly, and Daily, enter also the interval, such as "Every 2 Hour(s).

Start

Type the starting date, or select it from the popup calendar.

Expire

Select the type of expiration (such as Expire on) and type or select a date or number of times.