Skip to main content
Archived

Configure a set running job expiry time for each workspace (vs. each run/schedul

Related products:FME Flow
  • January 16, 2017
  • 1 reply
  • 19 views
fmelizard
Safer

***Note from Migration:***

Original Title was: Configure a set running job expiry time for each workspace (vs. each run/scheduled job)


Related to the FME Server 2017 "running job expiry time" (tm_ttc) parameter that cancels a job if it runs beyond a specified length of time:

https://knowledge.safe.com/idea/18984/configure-time-limits-for-a-job-and-alertcancel-if.html

-------

I'd like a time limit per workspace.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • September 28, 2017

If I am understanding correctly, this request is to have a "master" 'running job expiry time'? That is, no jobs would be able to run longer than a set time.

Helpful Members This Week

Community Stats

31,926
Posts
121,262
Replies
39,552
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.