Since the latest update "Cancel Timed Actions" is not working fine any more.
Has anyone issues with this?
App 3198 = Bathroom Douche Motion active
This is working for me in a quick test I just made (both Rule 5.1 rules).
What do both rules look like? Does hitting "Done" in both, particularly the one that is supposed to be "cancelled," help?
Anything cut off in the first rule, like one of the new options at the bottom?
Also, what about the other suggestion?
Don't know what you mean by that, but this rule works as expected, except the delay of 11 min can not be cancelled even after hit done or run action by hand in rule machine (other rule)
The repeat action is stoppable
Did you did a test that cancels a Delay?
There are additional options after the actions list that are cut off in your screenshot.
Perhaps some of them are different from what I tested and could affect the outcome.
1 Like
Sorry for the delete posts, l thought I had a test that shows canceling delays works, but, just the opposite.
Although, the canceling rule issues the cancel, and the rule with the delay āsaysā it was cancelled, the delay was not cancelled and it ran for the specified delay amount and the rule continued on.
And no, I did not check the new single threaded option.
1 Like
If you are having problems, what does "Scheduled Jobs" on the App Status page for the problematic rule (where the cancel didn't work), ideally both before and after the cancel during what would otherwise be the wait?
Mine had one job (the delay) listed before the cancel and nothing after.
I am finding this same issue. This is a rule which has worked fine before 2.3.9 and did not generate any errors. Now I am constantly getting the "Multiple simultaneous rule execution error"
I just made a couple of tweaks to the rule and turned on all the logging. I can see where the cancel did not work and the delay then resumed the rule later.
Here is the rule:
Here is Logs.
You can see run (1) ended with a delay.
Shortly after run (2) kicked in and executed a Cancel Timed Actions, which states it worked.
Then you can clearly see the delay from run (1) kicked off the rule to continue where it left off, after it should have already been canceled.
This also caused (earlier today) my alert to sound that the Sump was stuck, which in fact it was not. This has also never happened before even when this rule was triggering much more often than today.
2 Likes
Thatās the same thing Iām seeing. @bobbyD
Iām on 2.3.9.135.
2 Likes
I am sure now, it does not work any more (Cancel Delay)
when run this rule:
on 20:02:58.569 I cancelled the rule
@gopher.ny
@bravenel did you see this report? Seems like its not working right to me, see my post above with marked up logs.
2 Likes
Iām just now seeing this; will look into it and edit this post with findingsā¦
This bug found and fixed.... next release.
6 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
