- Scheduled triggers not auto-running on cron schedule - Manual trigger via API returning 500
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?
- Scheduled triggers not auto-running on cron schedule:
Trigger ID: trig_01LAgwXGG4z6W5TdoYWFD9cq
Cron: 0 16 *
Has missed auto-run on 2026-04-01 and 2026-04-02 at 16:00 UTC.
The next_run_at field never advances after the scheduled time passes.
- Manual trigger via API returning 500:
POST to /v1/code/triggers/{trigger_id}/run returns:
{"error":{"message":"An internal server error occurred","type":"api_error"}}
Request IDs: req_011CZdPmP622JKS2h6PFacrp, req_011CZfFWxCyrqRysokC3pviK
The request IDs are especially useful for Anthropic to look up the server-side logs.
What Should Happen?
- Scheduled triggers should auto-run at the specified cron time (0 16 * = 9am PDT daily)
- The
next_run_atfield should advance to the next day after each successful run - POST to /v1/code/triggers/{trigger_id}/run should return 200 and kick off the agent session
Error Messages/Logs
{"error":{"message":"An internal server error
occurred","type":"api_error"},"request_id":"req_011CZdPmP622JKS2h6PFacrp","type":"error"}
{"error":{"message":"An internal server error
occurred","type":"api_error"},"request_id":"req_011CZfFWxCyrqRysokC3pviK","type":"error"}
Steps to Reproduce
- Create a scheduled trigger via POST /v1/code/triggers with a cron_expression (e.g. "0 16 *")
- Wait for the scheduled time to pass
- Check the trigger via GET /v1/code/triggers/{trigger_id} — next_run_at does not advance
- Try to manually run via POST /v1/code/triggers/{trigger_id}/run — returns HTTP 500
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.90
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗