Hi @stevejames,

If you only have a single engine in the FMEServerJobSubmitter I'd recommend setting:

Submit Jobs: In Sequence

Wait for Jobs to Complete: Yes

This will launch an additional child engine to process these jobs meaning the parent job can wait until the child jobs submitted by the FMEServerJobSubmitter have finished before continuing to process features.

Once set, you'll see the output ports of the FSJS transformer changes from Submitted to Succeeded and Failed, allowing you to have different downstream responses depending on the result of the job.

In the Job History on FME Server you'll see the child has been run on the same Engine name but with the suffix @id where id is the Job ID of the Parent Job through which this additional engine was launched:

I have filed a request for our documentation team to include a warning in the FMEServerJobWaiter transformer Help that this transformer should not be used if your FME Server has one engine.

Brilliant @hollyatsafe that worked brilliantly.