It would be nice to control a job's running expiry time by which Queue it's been assigned to. At the moment Queues can be configured to a specific Repository, Engine, and designated a Priority level. So for example:
Fast Queue ( < 15 mins )
30 Min Queue ( 15 mins - 30 mins )
60 Min Queue ( 30 mins - 1 hr )
Slow Queue (1 hr + )
1) This would help when your limited to a small number of engines and have to manage a high volume of jobs.
2) It eliminates processes that may hang up an engine or two and cause the FME Server Job Queued List to rapidly grow. This could be to due to external sources. i.e. Database Performance Issues, Memory Constraints, CPU Constraints, and other constraints from a data source or target source perspective...
3) You wouldn't need to then set the running job expiry time parameter for each individual schedule or automation, which makes it easier for FME Admins and Authors.
4) It would be easier to designate the correct Queue for a schedule or automation. You wouldn't be mismanaging Queues and you'd be able to minimize the amount of time a job is waiting for an available engine on the Server.
Related to: https://community.safe.com/s/idea/0874Q000000TkrlQAC/detail
