core.noscript.text
If you have a long running gallery job that you know is looping or corrupting a lot of data, how can an admin or designer kill it now,
when waiting on timeout is not a viable option? In Server version 2023.1, is there anything short of rebooting all servers in the cluster?
Responses like "don't run bugged workflows" aren't answers.
Is there maybe a path to knowing which server and process id(s) can be killed with task manager?
Thanks
Solved! Go to Solution.
My brilliant co-worker found the answer in knowledge/server
I knew there had to be a way
Stop-a-Long-Running-App-Workflow-on-a-Private-Gallery
