With other time based Actions triggering it might not be an Action problem. I worked with another user some months back thinking a time based Action was not triggering which turned out to be an issue with the responder, not the Action. In that case the telnet trace showed the correct command was issued and ACKed with the responder device not reacting as expected. There was a problem where an Action was not being reenabled during the previous Action trigger and failed to trigger the next time but this was resolved with 02.06.04.
Reply To: why, o why? (actions issues)2017-12-21T19:47:15-08:00