Unexpected Activation of Tumbling Trigger Outside Scheduled Time

Question

A tumbling trigger was set to start at 12:00 AM on February 6, 2022, and end at 12:00 AM on September 11, 2022, with a recurrence of every 1440 minutes (once every 24 hours). However, it has activated unexpectedly without manual initiation. What could be the cause of this unexpected activation? Here are some configurations and screenshots of the trigger for reference:

Answer 1

Hello @Yujin Zhu (Shanghai Wicresoft Co Ltd)

There could be several reasons for this unexpected activation, such as:

1. Time zone issue: The trigger is set to run at 12:00 AM, but the time zone is not specified. If the time zone is not specified, daylight saving time (DST) events might affect when triggers run. For example, the start time shifts one hour forward when DST starts and one hour backward when DST ends. To avoid this issue, make sure to select a time zone when specifying the start time for the recurrence.
2. Recurrence shift and drift: For recurring connection-based triggers, the recurrence schedule isn't the only driver that controls execution. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior. For example, latency during storage calls, whether the trigger accesses a server that has more data, which the trigger immediately tries to fetch, and any failures or retries that the trigger incurs. To avoid this issue, make sure to manually adjust the recurrence to ensure that the recurrence time doesn't shift when DST takes effect.
3. Other factors: Other factors that can affect when the next run time happens, such as system updates, network issues, or other unexpected events. To troubleshoot this issue, you can check the trigger history to see if there are any error messages or unexpected events that might have caused the trigger to activate outside of the scheduled time. You can also check the system logs to see if there were any system updates or network issues that might have affected the trigger.

Wishing you happy holidays.

---

I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts but also assist other community members who may be looking for similar solutions.