Remote Triggers API returning 500 Internal Server Error

Resolved 💬 4 comments Opened Apr 4, 2026 by nexidneb Closed Apr 8, 2026

Description

The Remote Triggers API (/v1/code/triggers) is returning HTTP 500 Internal Server Error on all endpoints — list, get, and presumably run. This means scheduled triggers (cron-based remote agents) are not executing.

Reproduction

All of the following return 500 Internal Server Error:

  • GET /v1/code/triggers (list)
  • GET /v1/code/triggers/{trigger_id} (get)

Tested via the RemoteTrigger tool in Claude Code CLI. Multiple attempts over a ~15 minute window all fail consistently.

Impact

Scheduled triggers that run on a cron schedule have stopped firing. In our case, health monitoring triggers that run every 30 minutes stopped at approximately 04:31 UTC on April 4, 2026 (10:31 PM MDT April 3). No heartbeats have been sent since.

Notes

  • status.claude.com shows all systems operational — this subsystem does not appear to be tracked there.
  • No configuration changes were made to the triggers prior to the failure.
  • The issue appears to be platform-side, not client-side.

Environment

  • Claude Code CLI (latest)
  • macOS (Darwin 25.5.0)

View original on GitHub ↗

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