The recent update to Rule Machine seems to have messed up delayed actions for me. I can see in the logs that rule machine runs the appropriate action as a delayed action, but does not ever seem to execute the action later on. The screensaver is never started like it is supposed to.
When I take off the delay, the rule works exactly as expected and the screensaver starts right away. Any idea? This rule was working perfectly before, but something has broken it (and i haven't changed the rule on my end).
EDIT: well my hub locked up with the goodnight routine tonight too so maybe itās a hub wide issue. There were a few power glitches yesterday that shut off power to the house. I wonder if that corrupted something. Could use some guidance on how to troubleshoot and recover from this. I've got the new cloud backup service, so maybe I should restore from the point before problems happened...
It looks like the delayed action is at least getting scheduled, though you could check the "App Status" (gear icon) page for the rule to be sure. You should see something under "Scheduled Jobs" for the appropriate time, giving you a clue that it's likely this action. If your hub was off when this delay was up, it would have just been skipped--there's no "catch up" for one-time scheduled jobs that were missed.
To sort of "reset" the subscriptions and schedules in a rule, you can open it and either hit "Done" or "Update Rule" (basically the same thing, the latter just doesn't navigate you away from the page when you click it). That would be my best guess for what you could do here, unless you think your entire database is corrupted and that restoring from a backup would help.
How does one figure out of that is in fact the case? The rule machine problem persisted even after creating a new rule (via Add New Rule) that was the same.
I don't think you can, unless it tells you it was, in which case it should also restore from a last-known-good backup (in which case people usually notice that something they changed recently is missing). In your case, I'd start by checking the "App Status" page during the delay to see if anything is scheduled (and, I suppose, also make sure your hub's time settings are correct, though I can't see how that would affect the duration of a delay).
Usually when people see a rule that isn't "running" the actions as expected, it's actually a device problem. However, I see that you've tested it without the delay and noted that it works fine then. I suppose I'd still manually test the startScreensaver() command on the device itself (from the device page) just to make sure that's still the case since it can't hurt and could help identify a device vs. app issue.
Yup, I did that and it worked fine. That's why I'm so confused...
