[BUG] Cloud scheduled task "weekdays" preset runs Tue–Sat instead of Mon–Fri (off-by-one day-of-week)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
A cloud scheduled task configured with the "weekdays" preset via the Claude Code web UI (claude.ai/code/scheduled) runs on Tuesday through Saturday instead of the expected Monday through Friday.
Additionally, the session launched by the scheduler receives an incorrect date: the April 11 (Saturday) run's session reports "Today is Friday" — the date is off by one day.
Evidence: Run history
Full run history for the task (excluding MANUAL runs):
| Run date | Actual day | Ran (scheduled)? | Day reported inside session |
|----------|------------|-------------------|-----------------------------|
| Apr 13 | Monday | :x: Skipped — UI shows "Next run: Tomorrow at 3:00" | N/A |
| Apr 12 | Sunday | :x: (expected) | N/A |
| Apr 11 at 3:25 | Saturday | :white_check_mark: Ran | "Friday" ← wrong |
| Apr 10 at 8:18 | Friday | :white_check_mark: Ran | "Friday, April 10, 2026" ← correct |
| Apr 9 at 8:07 | Thursday | :white_check_mark: Ran | (not checked) |
| Apr 8 at 8:21 | Wednesday | :white_check_mark: Ran | (not checked) |
| Apr 7 at 8:05 | Tuesday | :white_check_mark: Ran | (not checked) |
| Apr 6 at 9:47 | Monday | :x: Only a MANUAL run | N/A |
| Apr 5 | Sunday | :x: (expected) | N/A |
| Apr 4 at 8:22 | Saturday | :white_check_mark: Ran | (not checked) |
Pattern is clear across two full weeks: scheduled runs fire on Tue, Wed, Thu, Fri, Sat. Monday is consistently skipped. Saturday is consistently included.
Evidence: Date mismatch inside session
When clicking on the April 11 run (session ID: session_01PRdszEvcNzXzxUWMSfHA1s), the session's conversation shows Claude believing "Today is Friday" — but April 11, 2026 is actually a Saturday.
This means the scheduler's internal clock is off by one day. The scheduler:
- Evaluates "should I run today?" using yesterday's day-of-week (thinks Saturday is Friday → Friday is a weekday → fires the task)
- Passes the wrong date to the session context
This explains the Tue–Sat pattern perfectly: the scheduler thinks Mon=Sun, Tue=Mon, Wed=Tue, ..., Sat=Fri. So "weekdays (Mon–Fri)" becomes Tue–Sat from the user's perspective.
Likely root cause
The scheduler appears to use a date/time value that is off by exactly one day (24 hours behind) when:
- Evaluating cron expressions to decide whether to fire
- Injecting the current date into the session context
This could be a timezone conversion bug — for example, if the scheduler converts JST (UTC+9) to UTC for cron evaluation but then subtracts the offset instead of adding it, or uses a date boundary that's 24h behind.
Downstream impact
My task prompt includes day-of-week logic:
- "If today is Monday: search Gmail for the past 3 days (Fri, Sat, Sun)"
- "If today is Tuesday–Friday: search Gmail for yesterday only"
Because the scheduler never fires on Monday and reports the wrong day, the Monday catch-up logic in my prompt never executes. Weekend emails are permanently missed.
What Should Happen?
- A task set to "weekdays" should run Monday through Friday only
- The date injected into the session context should match the actual calendar date
Steps to Reproduce
- Go to claude.ai/code/scheduled
- Create a new cloud scheduled task
- Set the schedule to "Weekdays" at any time
- Set the timezone to JST (Asia/Tokyo, UTC+9)
- Wait for a full week and check the run history
- Observe: task runs Tue–Sat, skips Monday, includes Saturday
- Click on a Saturday run and observe that the session reports the day as Friday
Error Messages/Logs
No error — the task completes successfully on the wrong days. The bug is silent.
Claude Model
N/A (infrastructure/scheduler issue, not model issue)
Is this a regression?
Unknown — this is the first time I've monitored a full week of runs.
Platform
Claude Code on the web (claude.ai/code/scheduled)
Operating System
Windows 11 Pro (client-side; issue is server-side in the cloud scheduler)
Additional Information
- Timezone: Asia/Tokyo (JST, UTC+9) — non-US timezone may be relevant to the bug
- Plan: Team
- Session ID for the April 11 (Saturday→"Friday") run:
session_01PRdszEvcNzXzxUWMSfHA1s - Possibly related to #24466 (Claude miscalculates day-of-week, off by one), which was closed as duplicate without a clear parent issue.
Screenshots
Task configuration and run history
This has been taken on Apr 13, 2026, which indicates skipping Mon. It also shows Sat running and next Tue running.
<img width="1917" height="938" alt="Image" src="https://github.com/user-attachments/assets/a01835e6-2732-486f-ab2c-3c21232fb7aa" />
Session showing wrong date (April 11 Saturday run reports "Friday")
<img width="1144" height="598" alt="Image" src="https://github.com/user-attachments/assets/da9801b1-0065-4853-9170-48f818a70c29" />
Full run history
<img width="1911" height="878" alt="Image" src="https://github.com/user-attachments/assets/4771ec19-5621-4c97-9f0d-0522b393b8ae" />
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗