We have a script that was triggered and should have been aborted by timeout already.
However, checking it on the client test tool, it seems that the script is still running (refer to picture below). Trying to "abort" does not do the trick.
Is it still running (it still appears in the running tab)? Is the only way to restart the SLAutomation process?
While the automation engine can mark a script as aborted, the script can only be aborted by the automation engine at points where the script interacts with the automation engine.
Because of how the script is written, this script is probably stuck in an endless loop, deadlocked, blocked inside a method call or ignoring ScriptAbortException.
Aside from restarting the SLAutomation process, the SLNetClientTest > Advanced > Automation > Managed Scripts has another context menu option "Abort C# code (forced)" which will force-abort the C# script by aborting the entire thread. Be aware that this method might cause side-effects because of the nature of aborting a thread (locks might not get freed, resources might not get released properly -- aborting a thread is like stopping a car by shooting the driver in the head: the car will stop but the damage is unclear).