# feat\(scheduler\): run fixed-time tasks in a chosen time zone · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/7b635bccaed0261ada4e3ff43e8f46c9fd9ae9fc)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 7b635bccaed0261ada4e3ff43e8f46c9fd9ae9fc

Requested commit: 7b635bccaed0261ada4e3ff43e8f46c9fd9ae9fc

Commit: 7b635bccaed0261ada4e3ff43e8f46c9fd9ae9fc

Tree: 480b82953f698f5be50b49bc1fc8a7a6d3bba91d

Author: Wills Manley

Committer: Wills Manley

## Message

```
feat(scheduler): run fixed-time tasks in a chosen time zone

A fixed-time task always ran on the environment's local clock, so a user in
another zone had to convert times by hand and redo it at every daylight-saving
change.

fixed_time schedules take an optional IANA timeZone, checked with Intl when
written. Without one, runs stay on the server's local time. The next run is
computed in that zone, so a time skipped when clocks spring forward runs that
much later and a repeated one runs once. A save that omits timeZone keeps the
stored zone, so older clients do not clear it; null removes it.

Web and mobile settings can set and show the zone, and the agent tools
describe it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [2c8bdf6177159d8fcd12a897d7c9311f6eb93237](https://git.cafe/pingdotgg/t3code/commit/2c8bdf6177159d8fcd12a897d7c9311f6eb93237?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/7b635bccaed0261ada4e3ff43e8f46c9fd9ae9fc?format=markdown)