Summary

A pipe scheduled for 7:00 AM fired at 6:00 PM. Scheduled pipe and cron times do not appear to honor the user's local timezone (this looks like a UTC vs local offset, roughly 11 hours here).

Reported

"A morning routine scheduled to run at 7 a.m. is just run at 6 p.m. Pipes aren't reading the time zone somehow."

"Let users set their timezone so reminders and pipes can run on local timezone." (separate user, same theme)

Reported on app 2.4.274 (Windows). Timezone handling is platform independent, so this likely affects all platforms.

Expected

A pipe scheduled for 07:00 runs at 07:00 in the user's local timezone.

Suggested fix

• Resolve cron schedules against the user's local timezone rather than UTC.
• Add an explicit timezone setting (defaulting to the system timezone) so scheduling is unambiguous and user-overridable.

Related scheduling fixes already shipped: #3684 (run a missed cron slot when the app restarts late) and #3607 (do not fire newly installed or stale cron pipes immediately). This is a distinct timezone-offset bug.

Source: in-app feedback, May 25 2026.