At the FME Flow (we’re looking at 2022.2 specifically) level, many people will be familiar with the ability to set time outs for queuing and running
Through the API you can also specify these by using the Job Directives: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/Job_Directives.htm
The scenario that we’re facing is there is an external process (not FME) that is setup to call a bunch of different workspaces depending on what is passed through. This is a process not managed/administrated by us.
Depending on the workspace called, we want to specify the running expiry at the workbench level, of course this could be doing with logic in the external process using tm_ttl/tm_ttc, but that would mean needing to release updated code each time we want to change this.
We’ve tried specifying tm_ttc as a workspace parameter (both published and private) but FME Flow doesn’t acknowledge it.
Talking with
Have we missed something?