Cron: Timezone: Reminders not returning to Whatsapp Group at the target time: raistlin28
Agent-created cron jobs omit tz; reminders fire in UTC not MYT
* Agent-created cron reminders are scheduled without a timezone (
* When a user specifies a timezone (e.g., “9:15 PM MYT”), the created cron job should include
* Agent confirms reminders in MYT (e.g., “Done! Reminder set for 9:15 PM MYT today”), but the cron job is created without a
* Example impact: 9:15 PM UTC = 5:15 AM MYT (+1 day).
* Agent-created cron job should include timezone, e.g.:
1. Reproduced multiple times with different reminder times (“9:00 PM MYT”, “9:15 PM MYT”, “9:20 PM MYT”).
2. Compared agent-created jobs vs CLI-created jobs.
3. Verified CLI works correctly when explicitly passing
4. Workaround: remove agent-created job and recreate via CLI with timezone.
* No specific config changes made for this; appears to be the agent
* Environment:
* ClawdBot version:
* Model: MiniMax M2.1
* Server OS: Debian (Hetzner CPX12, Singapore)
* Intended timezone:
* Agent-created job shows no timezone suffix:
* “in 8h” aligns with UTC interpretation (MYT is UTC+8).
* CLI-created jobs work when timezone is provided:
Summary
* Agent-created cron reminders are scheduled without a timezone (
tzGoal
* When a user specifies a timezone (e.g., “9:15 PM MYT”), the created cron job should include
tz: "Asia/Kuala_Lumpur"Current behavior
* Agent confirms reminders in MYT (e.g., “Done! Reminder set for 9:15 PM MYT today”), but the cron job is created without a
tz* Example impact: 9:15 PM UTC = 5:15 AM MYT (+1 day).
Expected behavior
* Agent-created cron job should include timezone, e.g.:
What I tried
1. Reproduced multiple times with different reminder times (“9:00 PM MYT”, “9:15 PM MYT”, “9:20 PM MYT”).
2. Compared agent-created jobs vs CLI-created jobs.
3. Verified CLI works correctly when explicitly passing
--tz "Asia/Kuala_Lumpur"4. Workaround: remove agent-created job and recreate via CLI with timezone.
Relevant config (redacted)
* No specific config changes made for this; appears to be the agent
cron* Environment:
* ClawdBot version:
2026.1.16-2* Model: MiniMax M2.1
* Server OS: Debian (Hetzner CPX12, Singapore)
* Intended timezone:
Asia/Kuala_LumpurLogs / error output
* Agent-created job shows no timezone suffix:
* “in 8h” aligns with UTC interpretation (MYT is UTC+8).
* CLI-created jobs work when timezone is provided:
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
