Routines UI shows multi-hour cron schedules in UTC without local timezone conversion
Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 21, 2026
Description
On https://claude.ai/code/routines, the schedule display is inconsistent between single-time and multi-hour cron expressions:
- A routine with cron
0 0 * * *(UTC) is correctly displayed as 9:00 AM for a user in Asia/Seoul (UTC+9). ✅ - A routine with cron
0 0,6,12,18 * * *(UTC) is displayed as 12:00 AM, 6:00 AM, 12:00 PM and 6:00 PM — the raw UTC hours shown as if they were local times. ❌ For an Asia/Seoul user the actual firing times are 09:00/15:00/21:00/03:00 KST.
Expected
Multi-hour cron schedules should be converted to the viewer's local timezone, same as single-time schedules.
Actual
Multi-hour crons render the UTC hour values without conversion, which misleads users into thinking the routine fires at different local times. Verified against the API: last_fired_at: 2026-07-21T06:03Z = 15:03 KST, matching the UTC cron, not the displayed times.
Environment
- claude.ai/code routines web UI (list + calendar view)
- User timezone: Asia/Seoul (UTC+9)
- Routines created via the remote-trigger HTTP API
🤖 Generated with Claude Code