[C8PJS-2.4.1.182] RM Rule Wouldn't Trigger

Not sure what happened (and my logs don't go back even a full day, so I can't see what went on before).

In any case, I got a "NOT Triggered - Already Running" message when it should have been triggered.

All I can guess is that the rule THOUGHT it was still running when it wasn't. It must have aborted in error previously. it also left the PB set improperly (

I ended up editing/saving the rule & manually turning off the PB. It then executed fine.

Is there any way to get a longer logging period/larger log?

The only way to make logs store more (besides unofficial solutions to save them elsewhere) is to reduce logging for apps or devices you don’t care about. If any in your logs are particularly chatty and not something you’re likely to care about, that’s where I’d start.

As for you rule, this wouldn’t be related to a required expression, though the steps you took can’t hurt regardless. It sounds like you have the deprecated option to prevent re-entrant triggering enabled on this rule, and turning that off (and finding another way to handle whatever concern this was trying to address if you had one) might be the best option, though someone can share more ideas if you share you actual Rule and a description of how you want it to work.

Unfortunately, as this glitch proves, there's no telling which of my automations might be problematic--so turning off logging ahead of time is a bit of a fool's errand.

I don't see that deprecated option in this rule--but I wouldn't rule out that it got set somehow, although I don't see it.

I just did a reboot with a database rebuild.

I was seeing a number of flaky things. Rules weren't all firing as expected, rules were VERY slow to kick off, etc.

Not sure what's going on.

I decided to stop using the PB and go with a time variable.

However, there doesn't seem to be any way to do a time offset in SECONDS--the offset is only in minutes and doesn't allow fractions. Thoughts?

@support-agent

Indeed, the "deprecated" option to prevent the rule from running multiple times WAS enabled.

However, I was only able to see that through when I edited the rule on my mobile (Android) phone. On my desktop/Firefox browser, I don't see that option.

I disabled that now.

It seems that the "already running" code has a tendency to think it's running when it really isn't.

I'm now seeing (with that option off) where the button event is somehow triggering multiple times (no idea what's up with that--I'm using a new, "easy" dashboard to display the button and pressing that on my phone).