Hi all,
I have an automation with a local calendar event trigger and it gave me some odd results today that I’d like to understand. Probably best formatted as a few numbered questions:
-
A few minutes before the event was due to start I decided I didn’t want the automation to run this time, so I deleted the event but it fired anyway. Best guess is some sort of cache that hadn’t caught up to the calendar change?
-
With the automation running, it’s then designed to wait for the end of the event before doing some additional steps. With the event deleted I tried to terminate the automation by setting the attribute “current” to “0”. I thought that was the correct procedure, but it carried on running… Though now I type it out, I think there’s a service I was supposed to call after that, right?
-
Finally, at the end of the deleted event, the wait-for-trigger actually triggered and the automation finished. Is this the same reason it fired in the first place?
Oh and bonus question 4: Is there any condition I can use to double-check that a calendar event definitely exists before it runs an automation?
Double bonus question 5: If the automation is running and then the event is deleted, is that something that can be spotted in a wait-for-trigger?
Huge thanks for any assistance! And have a great day.