Issue Summary

User had active scheduled automations that were supposed to run, but at the time they were supposed to run, the timezone was automatically updated instead. The message in the automation log is: "The automation was rescheduled to a new timezone: ..."

Steps to Reproduce

-

Expected Results

Scheduled automations should still be queued to run after a timezone update.

Actual Results

The timezone automatically updated by the scheduled automations did not run, and there weren't any error messages.

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available