You are here: Reference Manual > FME Server Core > Job Directives

Job Directives

Job directives control the job queue. The job queue is sorted by priority first and then by date submitted. Jobs with higher priority are executed before jobs with lower priority, even if jobs with lower priority are submitted first.

Job directives can be provided through the Transformation Services, FME Server REST API, and FME Server Console.

Job directives are also available through Schedules and the FME Workspace Subscriber.


An integer representing the request's priority level. Lower values mean a higher priority. Priority values must be greater than or equal to zero.

If priority is not set, the default is 100. The default range is 1 to 200, but there is no restriction other than being greater than zero. The highest priority is 1. A priority less than or equal to zero defaults to 100.


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.


The job queue tag distributes jobs between FME engines. If specified, job requests redirect to an engine that has been configured to accept the tag. For more information, see Job Queues.


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.


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.


See Also

Tags maximum time for job, job timeout, job time limit, hanging job, stop job, priority, rtc, tag, ttc, ttl