Thanks
@John Carter @Walter Koller,
Using the System.Diagnostics.Process.Responding property in a code stage to detect whether the user interface is responding.
This seems like a great idea. I'm quite experienced with VBA and okay at C++, however no experience in C# syntax or BP's likely varied C# syntax.
I've googled but am in over my head without taking a 5-10hr LinkedIn/Udemy C# course. Any suggestions on a starter code block, or template to adapt?
Using CMD linetasklist /FI "STATUS eq NOT RESPONDING" /FI "IMAGENAME eq chrome.exe"
After some particular actions from BP I would like to poll the status every 5 seconds and loop until status <> "Not Responding". BP will handle kill process logic based off max loop. I think using CMD would be causing my system a hassle, and BP as I'd be shifting active windows; either using CMD itself, or Windows "Run" program.
I think coding is the cleanest way, as the system is aware of the responsiveness with or without Task Manager open, meaning I should be able to poll and call the current status without opening any additional applications.