It would be very useful to be able to set a "Translation Timeout" as a workspace translation parameter, like this:
If the total runtime of a translation exceeds this timeout configuration, then the translation immediately terminates with a timeout error.
To my knowledge, currently we can only control job expiration times for jobs submitted to FME Server, as an advanced parameter of the FMEServerJobSubmitter transformer. That's great for many use cases, but it doesn't help with controlling timeout issues for job chains run locally with FME Desktop, or for hybrid desktop/server workflows. I feel like a more object-oriented approach would involve allowing the workspace author to set a default timeout from within the workspace, regardless of whether it will be running on desktop or server.
This translation timeout parameter could then be linked to a published or private parameter, depending on the use case. As a published parameter, the workspace could then be cleanly integrated into a controlled complex job chain.
Perhaps there are some under-the-hood complexities that I am unaware of that would prevent this type of functionality?
