[BUG] Scheduled triggers API returns HTTP 500 on all endpoints (list, get, run), create returns 200 but trigger not persisted
Resolved 💬 4 comments Opened Apr 4, 2026 by robgoudzwaard Closed May 14, 2026
Description
The scheduled triggers API (RemoteTrigger) is returning HTTP 500 errors on all endpoints. A create call returns 200 but the trigger does not appear in the UI and cannot be retrieved via the API.
Steps to reproduce
- Call
RemoteTriggerwithaction: "list"→ HTTP 500 - Call
RemoteTriggerwithaction: "create"with valid body → HTTP 200, returns trigger IDtrig_01WzbVtuNRGjWeGgdCZ7dZim - Call
RemoteTriggerwithaction: "get", trigger_id from step 2 → HTTP 500 - Call
RemoteTriggerwithaction: "run", trigger_id from step 2 → HTTP 500 - Visit https://claude.ai/code/scheduled → Shows "Failed to load scheduled tasks"
- Created trigger does not appear in the UI
Expected behavior
- All API endpoints should return valid responses
- Created trigger should appear in the UI and be runnable
Environment
- Claude Code CLI (macOS)
- Model: claude-opus-4-6 (1M context)
- Date: April 4, 2026
- Environment ID: env_0194sBUD5Cscjh6VnbdiLhsx (Default, anthropic_cloud)
Error responses
All failing endpoints return the same error format:
{"error": {"message": "An internal server error occurred", "type": "api_error"}, "type": "error"}
Related issues
- #42662 — Scheduled triggers not auto-running, manual trigger returns 500
- #42582 — Remote Trigger /run returns HTTP 500, trigger auto-disables
- #43409 — Web UI "Failed to load scheduled tasks"
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗