Hmm we already blanked out the repo so this is not related to the old plugin.
We did play with this trigger a bit recently, maybe @Osama has some ideas.
Any more info in your logs @Festinger, what is the message?
Can you create a new automation rule from scratch for same action, does that work around the issue?