Fortunately we have reproduced this issue and our developers are now investigating it. You can check it here
Meanwhile you can try the following:
The scheduling setup is quite complex and there are lots of connections that might be messed up. The behavior you describe leads me to the conclusion that the storage is actually the reason for that behavior. And therefore I would like to ask you to drop the database or only the tests and testlists collections which will ensure saving your previous results. You could use Robomongo
to connect to the storage and select only the above mentioned collections to prevent the loss of results.
If the above suggestion does not bring any success please execute the faulty test list and generate the application log
. Along with that collect the remote executor log
as well. Please clear both logs prior starting the faulty execution to ensure only relative records will be captured within.
Hope to hear from you soon.
Telerik by Progress