Thank you for contacting us on that matter.
When a Test List is sent for execution on a remote server, this is done by the Scheduling Server. If there is already running list on this Remote Server, the new Test List will be queued and executed after the current one completes. There is no straight forward mechanism for stopping a run on the Remote server once it is queued.
The only thing you can do is kill the process of the Test Runner (Telerik.TestStudio.Scheduling.Client.exe) and then start it again. However if there are other queued test lists to run, upon restart of process it will start them also.
If we know your complete use case and more information why this situation happens, we can probably give you some other advice or direction to work on and resolve your situation. We have implemented mechanism in Test Studio to show a Remote Runner as Busy
when it is running tests, also you can see the status of all remote servers
in a scheduling setup.
What do you think your problem comes from and how do you imagine the product should work to avoid this situation? You feedback and opinion is important to us.