Job Directives

Job directives control various aspects of how jobs run. Job directives can be provided through the Transformation Services, FME Server REST API, and FME Server Console.

Job directives are also available through Automations workflows that contain a Run a Workspace action or Schedule trigger.

tm_rtc

Runs a job until it is explicitly canceled. The job continuously restarts, regardless of whether the job completed successfully, failed, or the server crashed or was shut down. Valid values are true or false.

tm_tag

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.

Tip: To control the priority of job requests, set the priority of the job queue.

tm_ttc

The time, in seconds, 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.

tm_ttl

The "time to live" in the job queue in seconds. This is used in cases where jobs are time-sensitive and can become invalid or stale while waiting in the job queue. If a job is queued longer than "time to live", it is removed from the queue instead of redirecting to an engine.

Note: This directive is enforced only during periods when FME Engines are free, which comprises the time between completion of a job and the start of the next queued job.

Job Directives

Examples