[BUG] RemoteTrigger `run` endpoint returns HTTP 500 for valid trigger

Resolved 💬 4 comments Opened Apr 7, 2026 by azher-ratnani Closed Apr 11, 2026

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?

Trigger trig_01FzzBtAJS267rY9ZxPoEYSv was created successfully (HTTP 200)
and GET returns healthy config with all fields populated. However,
POST /v1/code/triggers/{trigger_id}/run consistently returns HTTP 500:

{"error":{"message":"An internal server error occurred","type":"api_error"}}

Attempted 3 times over ~20 minutes — same result each time.

Trigger config:

  • Environment: env_0136T83xnctG8FAuA2HfLchV (anthropic_cloud)
  • MCP connections: Granola, Slack, Notion
  • Git source: https://github.com/azher-ratnani/fleek-knowledge-base
  • Model: claude-sonnet-4-6
  • Cron: 53 3 * (scheduled runs not yet tested)
  • Created at: 2026-04-07T10:01:00Z

Request IDs:

  • req_011CZpDdQnNLrFM9D9Ba37UH
  • req_011CZpDdqpWXZAYMZFt1Xj2r
  • req_011CZpFXYhBpLjJBPBnCAiv9

What Should Happen?

The trigger should run the scheduled job.

Error Messages/Logs

{"error":{"message":"An internal server error occurred","type":"api_error"}}

Steps to Reproduce

  1. Create a remote trigger with MCP connections (Granola, Slack, Notion) and a git source:
  • POST /v1/code/triggers with valid body (returns HTTP 200)
  1. Verify trigger exists:
  • GET /v1/code/triggers/trig_01FzzBtAJS267rY9ZxPoEYSv (returns HTTP 200 with full config)
  1. Attempt manual run:
  • POST /v1/code/triggers/trig_01FzzBtAJS267rY9ZxPoEYSv/run
  1. Returns HTTP 500 consistently across 3 attempts over 20 minutes

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.90 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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