There is no possibility to activate a topic on cancellation.
This can happen if the 'queue or job expiry time' exceeds their time or someone cancelled the job by accident.
Jobs can exceed due to occupied engines, expired licences, bigger than normal dynamic input datasets (or even bad scripting).
I think this is a great idea, while it's an edge case it would be handy
Hi @meijer, I tested a couple different workflows in FME Server 2019.0, and was able to have a workspace "failed" (or cancelled) by exceeding the 'Queued Time' or 'Running Time' notify a Topic – this includes manual cancellation.
The first workflow is new for FME Server 2019.0 and makes use of the new Automations feature. If you build a workflow that includes any Run Workspace Action, the cancellation will cause the workflow to follow the 'Failed' port.
'
The second workflow is more difficult to setup – as it requires the user to set the "Topics to Notify (Failure)" during publish time. But this is also valid.
'
Hope that helps! Please let us know if we can offer more detailed explanations. I have changed the status of this idea to In Beta.
Great, I ll check it out. Thanks a lot for listing and replying!
Note: FME Server 2019.0 was released on April 2 2019. This idea status marked as Released.
Hi @rylanatsafe, I don't know if I undestand this correctly, but has this actually been released? I know you can notify a topic or set an action in an automation for failed jobs, but "failed" includes both "failed" and "cancelled", and I understand the purpose of this idea was to differentiate one from the other