Skip to main content
  • EN

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 @todd_davis we’re both sure you used to be able to do this (specific run time limits at the workspace level).

Have we missed something?

Hi @hkingsbury, 

I’m asking around internally to see if something similar is possible and update this post if something comes up. 

The only thing I can think of is using a FMEFlowJobSubmitter in a parent workspace to run a child workspace and use those parameters.

Hi @hkingsbury, 

I’m asking around internally to see if something similar is possible and update this post if something comes up. 

The only thing I can think of is using a FMEFlowJobSubmitter in a parent workspace to run a child workspace and use those parameters.

Thanks Sienna, I thought about raising an idea, but I’ll wait to hear back from you

Hi @hkingsbury, 

I think this is worth raising an idea! 

The only other suggestion is to do a datetimestamp, then calculate the time running, if it’s too long then use a terminator, but that’s understandably not a great workaround.

 

Sorry we couldn’t think of anything else to meet your needs here!

Hi guys, I’ve had some problems with the FMEServerJobSubmitter in previous versions. I have topic published on a child workspace for success or failure. Somehow the transformer doesn’t make these topics run, I have to change to a httpcaller and specify the topics in the directive 

 

Hi guys, I’ve had some problems with the FMEServerJobSubmitter in previous versions. I have topic published on a child workspace for success or failure. Somehow the transformer doesn’t make these topics run, I have to change to a httpcaller and specify the topics in the directive 

 

you might want to create a new thread - this answer seems unrelated to the initial question. 

I have made an Idea for this:
https://community.safe.com/ideas/process-timeout-for-workspaces-34637

Reply


Community Stats

30,370
Posts
115,382
Replies
38,145
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.