In the Alteryx server system setting, we have a parameter called "Cancel jobs running longer than (seconds)" which automatically kills the scheduled jobs after the given seconds, without considering the queue time.
i.e, Right now, four scheduled jobs are triggered from the gallery, and the system is able to run two parallel jobs. The last two are obviously in the queued state. The second set of 2 tasks is started running, based on the first set of job completion. From that point when the job started running after queue time (Actual Execution Start time), only the parameter should work, but unfortunately, it kills the job without considering the queue time.
Hello @Ariharan
We had faced similar issues on our landscape as well, we created a script that checks run time based on AlteryxEngineCMD running in task manager and cancels it once mentioned time surpasses.
Hi @AsmiDesai ,
Thanks for the reply. If possible can you please share that script.?
Regards,
Ariharan.R
Hello @Ariharan ,
Check this thread on stack overflow:
https://stackoverflow.com/questions/14385122/how-to-kill-a-windows-process-running-longer-than-30-mi...
The windows process for Alteryx workflow would be AlteryxEngineCMD.exe.
This should help.