So the 'Cancel or quit' option is literally doing a cancel, not a cancel recursive. That's unfortunate...
I haven't tested this, but I think it would work...clunky as it is... Instead of selecting the cancel/quit option, do the 'execute another task' option. Then build a task (script) that identifies the RunID of the object that invoked it (i.e., your workflow with this MRT setting) -- I believe &$ACTIVATOR# should work -- and then does a :CANCEL_UC_OBJECT(&RunID#,ALL). That should do the cancel-recursive you're looking for.
Original Message:
Sent: Sep 19, 2024 07:54 PM
From: LoriKeehr608694
Subject: Workflow set to cancel at a specific time - active job within it is NOT cancelling
We have a situation where we are required to cancel a workflow entirely including all the jobs within it if a specific time is reached, regardless of if jobs are running. We have a Max runtime set on the workflow and to take the action of Cancel or quit this task if the runtime is exceeded, however this is not killing the job that is running. Are there any suggestions on how to address this type of scenario?