claude-code - 💡(How to fix) Fix Scheduled routine/trigger fails to fire at cron time

TL;DR

The scheduled routine may not have fired due to an issue with the scheduler's calculation of the next run time, potentially related to the unusual offset in the next_run_at timestamp.

Guidance

• Verify that the cron expression 0 15 * * 1-5 is correctly interpreted by the scheduler, ensuring it aligns with the expected firing time of 3:00 PM UTC (11:00 AM EDT) on weekdays.
• Investigate the scheduler's behavior regarding the calculation of next_run_at timestamps, particularly how it handles offsets and whether it correctly snaps to the cron expression schedule.
• Check if there are any platform-specific settings or configurations in Claude Code routines that could affect the scheduling behavior, such as timezone settings or scheduling precision.
• Consider testing the routine with a different cron expression or at a different time to see if the issue persists, which could help isolate the problem.

Example

No specific code snippet can be provided without more details on the scheduler's implementation, but ensuring the cron expression is correctly formatted and understood by the scheduler is crucial.

Notes

The provided information suggests a potential issue with how the scheduler calculates the next run time, possibly due to the routine's creation time or an incorrect interpretation of the cron expression. Further investigation into the scheduler's logic and platform settings is necessary to resolve the issue.

Recommendation

Apply a workaround by adjusting the cron expression or the routine's configuration to better align with the scheduler's expected behavior, as the root cause seems related to the scheduling mechanism rather than a straightforward fix.