Automation card says 12 AM while the stored task runs at 3 AM
I asked Codex to resume a task at 3 AM in Israel.
The app created the automation and the card says Daily at 12:00 AM. The automation database says the next run is July 11 2026 at 3:00 AM in Israel.
Here is the exact problem.
- Windows timezone is Israel Standard Time.
- The Codex runtime reports Asia/Jerusalem.
- If the schedule uses hour 0, the card says 12:00 AM but the backend stores midnight UTC, which is 3:00 AM in Israel.
- If I make the timezone explicit and schedule 3:00 AM in Asia/Jerusalem, Codex accepts it but the backend stores 3:00 AM UTC, which becomes 6:00 AM in Israel.
So the card and the scheduler are not using the same timezone. Adding the correct timezone makes the offset happen again instead of fixing it.
What I expected.
I should be able to ask for 3:00 AM in my local timezone. The card should say 3:00 AM and the task should run at 3:00 AM.
What actually happened.
I can make the task run at 3:00 AM only by storing midnight. Then the card tells me it will run at 12:00 AM. If I store 3:00 AM with Asia/Jerusalem, the task moves to 6:00 AM.
Environment.
Codex App 26.707.3748.0
Windows build 26200.8655
Architecture AMD64
Automation type heartbeat
This looks related to issue 26633, but this reproduction is on Windows with a heartbeat automation and shows the card and stored execution timestamp disagreeing for the same task.