Scheduled routine/trigger fails to fire at cron time

Resolved 💬 2 comments Opened Apr 20, 2026 by ketushah Closed Apr 20, 2026

Bug

A scheduled routine (remote trigger) with a valid cron expression did not fire at its scheduled time.

Details

  • Trigger ID: trig_01N21vj1CQoAgQnYVe423njx
  • Cron expression: 0 15 * * 1-5 (3:00 PM UTC / 11:00 AM EDT, weekdays)
  • Routine name: "Daily Briefing"
  • enabled: true
  • next_run_at: 2026-04-20T15:03:38.546279523Z
  • Observed at: ~11:07 AM EDT (15:07 UTC) on Monday, April 20, 2026 — routine had not fired and no in-progress run was visible on the status page.
  • Manual /run worked fine — the routine executed successfully when triggered manually via the API.

Expected behavior

The routine should have automatically fired at or shortly after 2026-04-20T15:03:38Z.

Actual behavior

No run was initiated. The status page showed no in-progress or recent run. A manual trigger via the API worked immediately.

Notes

  • The routine was created on 2026-04-17T17:36:51Z (Thursday). This was its first scheduled Monday run.
  • The next_run_at timestamp has an unusual :03:38 offset rather than :00:00, which may indicate the scheduler is calculating next run from creation time rather than snapping to the cron expression. This could be related to the missed trigger.
  • Platform: Claude Code routines (claude.ai/code/routines)

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗