There appears to be a bug in killing active run delays via the runs module in current 099 versions. The run delays execute, but when looping through the runs object and killing any run – execution does not happen. This behavior is happening regardless of killing all runs indiscriminately, as well as passing through a run group and killing based off run group.
Attached is a unit test .tox demonstrating the behavior. The kill works perfectly fine when running in 099 version 2017.16620, but does not execute at all when running in version 2018.2500.
Windows 10 Pro
Build 099 2017.16620 : working
Build 099 2018.25000 : not working
base_killtest.tox (1.9 KB)