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. When finished, click OK.
Tip: You can test a workspace that is initiated by a Schedule trigger, regardless of the times the Schedule is configured to execute. See Testing a Schedule-Initiated Workspace.
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.
Run Immediately: When checked, the task starts as soon as it is added to the Schedules table. When unchecked, the page allows you to specify Start Time.
Start Time - Date and time the task is to start. For more information, see Specifying a Future Time.
Recurrence: Specify how often the task repeats. You can specify:
- Repeat On Interval: Repeats in intervals from a list of predefined units.
- CRON Expression: Repeats based on your own cron expression.
- Only Occur Once: The task runs once only at the specified Start Time.
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.
If Repeat on Interval is specified, the schedule does not adjust when switching between Standard Time and Daylight Saving Time.
|Field||Required||Allowed Values||Allowed Special Characters|
|Seconds||Yes||0-59||, - * /|
|Minutes||Yes||0-59||, - * /|
|Hours||Yes||0-23||, - * /|
|Day of month||Yes||1-31||, - * ? / L W|
|Month||Yes||1-12 or JAN-DEC||, - * /|
|Day of week||Yes||1-7 or SUN-SAT||, - * ? / L #|
|Year||No||empty, 1970-2099||, - * /|
For more information about the cron format, see this FME Community article.
The following example shows a recurring task entry in the table:
In this example, the task recurs every four days starting on 01-Feb-2018 at 8pm and ending on 01-March-2018 at 10am.
Schedule Does Not Expire: When checked, the task has no end time. When unchecked, the page allows you to specify End Time.
End Time: Date and time to stop running the task. For more information, see Specifying a Future Time.
Repository: Name of the repository in which the workspace resides.
Workspace: Workspace the task is to run.
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.
If desired, specify the Notification Service topics to which to send a notification if the task executes successfully (Post to Topic on Success) or unsuccessfully (Post to Topic on Failure). For more information, see Monitoring FME Server Events from Topics.
Job Queue (optional): The job queue in which to run the job. The specified queue overrides the queue of the repository to which the workspace belongs. If not specified, the job is placed in the job queue of the repository.
Queued Job Expiry Time (optional): The length of time 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.
Running Job Expiry Time (optional): The time a job will remain in the running state. This directive is used to ensure that a job does not hang and block an FME Engine indefinitely. The minimum allowable value is 1.
Run Until Cancelled (optional): If checked, the job runs continuously, even after a server shutdown or crash, until it is explicitly canceled.