You are here: Web User Interface > Using the Interface > Schedules > Adding a Scheduled Task

Adding a Scheduled Task

To add a scheduled task, navigate to the Schedules page and do either of the following:

  • click New.
  • Select a task from the table, and click Duplicate. This alternative allows you to add a task by duplicating an existing one, and then editing it.

Enter or edit the following information to define the task:

General Settings

Name - Name of the task

Category - Name of the general category or group to which the task belongs.

This name can be used to organize tasks into site-specific types as required.

Task names must be unique within the table.

Description - Description of the task.

Enabled- Check to enable the task.

Workspace Settings

Name of the workspace which the task is to run, and the repository in which the workspace resides.

Once the workspace is specified, any published parameters of the workspace display. You can modify these parameters, if desired. The changes take effect when the task is run.

Schedule Settings

Start Date - Date and time the task is to start.

Checking the Immediately box causes the task to start as soon as it is added to the Schedules table. Unchecking the box allows you to specify a future start date and time.

Repeats- Specify how often the task repeats. You can specify once-only, repeating in intervals from a list of predefined units, or repeating based on your own cron expression.

Note: cron expressions must be configured according to the time zone of the FME Server that runs the task. All other times can be expressed according to your local time zone.

End Date: Date and time to stop running the task.

Notification Settings

If desired, specify the Notification Service topics to which to send a notification if the task executes successfully (on Success) or unsuccessfully (on Failure).

Advanced Settings

Job Priority (optional) – The priority of the job that is run by the workspace.

Job Routing Tag (optional) - To associate the job with a specific FME Engine, specify the name of the job routing tag associated with that engine. For example, if Engine 1 is configured with the "utility" tag in the FME Server configuration file, as TM_ENGINE_1=engine1:utility, specify utility. For more information about job routing, see Configuring Job Routing.

Queued Job Expiry Time (optional) - The length of time, in seconds, after which a job that is waiting in queue does not execute. If the job does not execute before this time is reached, it remains in the queue until it is ready to execute, but execution is not attempted. This directive is useful for time-sensitive jobs that you do not want to run after the specified time is exceeded.

See Also