Much appreciated, please keep it under consideration. With sufficient warnings, I think this would be useful because once the BES client is tied up in an action, it won’t execute any new actions that we might send to take corrective actions. Even if we were to “stop” the offending action, the client is still tied up waiting for the external process. Nothing short of restarting the BES client can clear it, and even then we may have trouble with subsequent actions because the stuck external process has the __Download folder locked.
In my environment, I’ve already had to implement a process that is crude and I hate very much. I have a scheduled task running every half, checking with qna.exe to find processes that are child processes of besclient.exe, and have been running more than 2 hours, to kill them.