Hi @stezi ,

What Engine Management rule do you have set up to cancel running jobs?

You are correct, the job retry in Automations is for failed jobs; intentionally cancelled jobs will not be resubmitted.

Let me know your thoughts!

Kezia

Hey Kezia. Where can I configure this? I cannot find anything in the Engine Management section and the doc.

Hi @stezi ,

There isn’t an engine management rule to cancel running jobs. We do have Advanced settings on the Run Workspace page to cancel jobs based on Queued Job Expiry Time and Running Job Expiry Time. You can also use the FME Flow REST API calls to configure some sort of workflow. 

An idea to resubmit a cancelled job could be to set up an Automation with the FME Flow Systems Event trigger and use the Filter Action to filter for messages that contain the word “Cancelled”. A cancelled job will log like this:

7662	Error Message Logged	Event Description: Triggered whenever an error message is logged to fmeserver.log.Event Title: Error Message LoggedMessage: Job 46: Cancelled running job

You can then author a workspace to resubmit the job using the REST API call. 

Some resources that may be helpful:

• System Events
• System Events Trigger
• FME Flow REST API V3 (can test with V4 too)
• Getting Started with Queue Control

Please let me know if I’ve misunderstood your question.

Kezia

Your second idea seems to be what I’ve been looking for, although I do not fully understand the part “You can then author a workspace to resubmit the job using the REST API call.“.

I think it would be nice to have a checkbox “Retry on canceled” in the “run workspace” element in an automation that would manage everything for the user :)

Hi @stezi ,

There are couple of FME Flow REST API endpoints that you can use to submit/execute the job.

Here is an example workspace for gathering information on a failed job. The workspace that you author can be tailored to submit the job using the appropriate endpoint.

If the job has a max queue time set, it’s assumed that when expired, the job will not be submitted. The job has not failed and has not been cancelled yet, just sitting in the queue. Then it will require manual intervention to execute the job. Having Retry on Cancel could be a good idea... I’d recommend submitting an idea here and share your use case.