We've pushed a fix and have rescheduled affected jobs.
Posted Oct 27, 2022 - 05:50 UTC
Identified
A recent change to our scheduling system caused any timer-based triggers to run in UTC, instead of the user-configured timezone. We're investigating the issue and will post an update when correct scheduling has resumed.
Posted Oct 27, 2022 - 05:14 UTC
This incident affected: Backend (Workflows - Timer).