Hi

One FME Server engine can only run one single job (workspace) at at time. If all engines are busy, subsequent jobs will enter the job queue and will be processed on a first-come/priority basis whenever an engine becomes available again.

The only exception to this rule is when using a FMEServerJobSubmitter with "Wait for server job to complete" set to yes, you will be able to execute one child workspace at a time from within a parent workspace, within one single engine. From the help: "When Wait for Server Job to Complete is set to Yes, and multiple FMEServerJobSubmitter transformers are linked to manage the workflow of multiple jobs on the same FME Server, all jobs run as child processes of the same FME engine that is engaged by FME Server to run the first job. No other FME engine is engaged. As a result, child jobs do not appear in the FME Server job queue or job history, and do not have their own job_id's. Additionally, all job logs are included in the job log of the parent (controller) job"

David

If it's for performance reasons, look in your workspace for anywhere you can use Parallel Processing (most transformers with a Group-By setting have this capability). That will allow a single engine to run multiple processes at the same time (but still only 1 job)

You can use the TAG in your workbench to using just one engine.

TM_ENGINE_1=panaka:engine1:fast

Check the documentation: http://docs.safe.com/fme/2013/html/FME_Server_Admi...