Running actions manually is/was not a problem.
Deleting and re-creating a Triger fixed the problem.
So somehow the rule lost a trigger subscription or whatever it was?
Thank you for the response.
Actually just deleting and recreating just a Trigger fixed the rule.
But I am curious, is it any reasonable explanation why did it happened?
It could be worse. We took a lightning hit Saturday night, and it knocked out my LAN by frying 3 ethernet switches, even though they appeared to be fine (blinking lights). Had a super dumb home until 20 minutes ago.
I have (I think) seen times immediately after a firmware update that triggers will fire but rules don’t run. If I “update rule” it works. Irritating but not worth my time to debug since it only appears to happen after update.
In my case this was not related to any updates or any other modifications. It simply happened in a middle of nowhere. Nothing worked until I deleted and recreated a Trigger.
Now I have to rebuild this rule but I am confused what exactly should I do?
Simply attempt to clone this rule or started it from scratch with attempt to export all actionsa from the old rule and reimport them into a new one?
I think your suggestion is latest (recreate rule and reimport all actions).
But something bad is going on which makes me really unhappy.
UPDATE
So rule is recreated from scratch with importing all actions from the existing one.
Of course, this new version is working but the question is how stable it will be this time.
Now wait, this is not even the same rule, and you're talking about a completely different issue: (unused)
(unused) is an artifact of the UI, and it's certainly possible for it to get out of synch on any given page render, depending on the actual sequence of steps -- but that won't persist. Open the Manage Conditions page... (unused) would have nothing to do whatsoever with your failed trigger. A failed trigger like that smells like a database corruption (hence my suggestion to create a new rule).
Look, I know you get on these issues as if the sky is falling, but it's not. Please start a new post if you have a different problem than originally posted. Don't bother posting about (unused) unless it is clearly a repeatable problem, which means that I could reproduce it.
Why do you think this rule is different?
No, this is exactly the same rule and exactly the same problem reoccurred (i.e. Trigger Event is present but rule fails to run)
After few attempts to update rule and reload a GUI this "unused" indicator still did not go away.
This time I did recreate a rule from scratch and it does work but the question is:
How stable this new version will be.
And no, sky is not falling. But all the observed failures simply make near no sense.
OK, that is not what you posted above, and would have been helpful to know.
What "new version" are you talking about? RM has had very few changes recently, none related to what you're talking about. Rule triggers are known to be working fine (except for you).
I am talking about new version of that failed rule which I recreated from scratch per yours suggestion. But I recreated this rule after it fails again the same way. First fix (which worked few times) was just to recreate a trigger.
I guess, I made my point very clear but apparently not clear enough.
I did performed a SoftReset and Reboot .
This suppose to cleanup a corrupted database (if it was corrupted). Is not it?
Somebody else in this thread mentioned a failing Triggers ufter hub was updated.
So, not only my case.
