scheduler: scheduled task times shown in UTC instead of local/system time (IST)#18632

Screenshots from the original report:

1. System clock (local, IST): 16:34, 12-10-2026 system clock showing 16:34 12-10-2026

2. Scheduled task row showing UTC time: "Daily at 16:31 · Next run in 5h" scheduled task Astra Evening - Daily at 16:31, Next run in 5h

Accepting this as a bug, but a narrower one than reported: the missing label is the bug, not the timezone the schedule runs in.

On main, fixed-time schedules run in the server's local timezone. ScheduledTaskService computes the next run from DateTime.nowInCurrentZone on the server, and nextScheduledRunAt sets the wall-clock timeOfDay in that zone. On a UTC VM, "16:31" means 16:31 UTC, so "Next run in 5h" is correct. There's no timezone setting.

What's wrong is that nothing tells you that. The Run at time picker and the Daily at 16:31 label show the raw timeOfDay with no zone. When the client and server are in different zones, you end up scheduling in a zone you can't see.

The fix in scope is to show the server's timezone in the picker and the label (for example Daily at 16:31 UTC). Converting schedules to the client's timezone, or adding a per-task timezone, would change how schedules behave, so that should be an Ideas discussion.

Workaround for now: enter times in the VM's timezone (UTC). For 16:31 IST, use 11:01.

Correction: I first wrote that #18653 had fixed this on web. It was reverted the same day in #22230, so main has no timeZone on the scheduled-task list and no zone on web or mobile. #18632 is still fully open.

From the revert, the full IANA name on every label ("Weekdays at 09:00 America/Los_Angeles") was too long for the automations panel. Before writing anything, what would you like?

• Format: a short abbreviation ("UTC", "PDT") or a UTC offset.
• When: always, or only when the server's zone differs from the client's.
• Where: the "Run at" picker only, or the list rows too.

Tested current main 70e5e384da with an isolated Linux dev server and the real web client. In Settings → Scheduled Tasks, created a daily 16:31 task. At 22:31 UTC the row read Daily at 16:31 · Next run in 18h, with no timezone label. Both the browser and server report UTC, so this confirms the missing label but does not verify the IST/browser versus UTC/server mismatch. The available browser tools cannot change the browser timezone.

Can you check on a current build from your IST client and share the schedule row and next-run countdown, plus whether the task was created in the Run at picker or by an agent? The original report is from an older nightly; the earlier labeling fix was subsequently reverted in #22230. Leaving this open for that cross-timezone check.

Checked on current main (70e5e384da) with the server and browser in different zones: server started with TZ=UTC, browser in Australia/Sydney (UTC+11, AEDT).

At browser time Thu 22 Oct 10:07 (server time 21 Oct 23:07 UTC), I created a daily task in Settings > Scheduled Tasks with the Run at picker, set to 13:10 (about 3 hours ahead on the browser clock).

• Picker: shows 01:10 PM (browser locale), no timezone.
• Row: Daily at 13:10 · Next run in 14h. The label has no timezone and uses 24-hour format, unlike the picker.
• 14h matches 13:10 UTC on the server, not 13:10 Sydney (which would read about 3h).

So the row and picker are the same wall-clock number with no zone, and the countdown is the only hint the zone differs. Created via the picker only; I did not test an agent-created task.

Row:

Picker: