[BUG] RemoteTrigger action 'run' fails with 'trigger_id: Field required' (HTTP 400)

Resolved 💬 1 comment Opened Apr 9, 2026 by chulwoongpark Closed Apr 9, 2026

Bug Description

RemoteTrigger(action: "run", trigger_id: "...") always fails with HTTP 400 trigger_id: Field required, while get and update actions work fine with the same trigger_id.

Reproduction Steps

  1. Have an existing trigger (e.g., trig_01Y9HX7i8hedRs28SEBHBJzs)
  2. Verify get works:

``
RemoteTrigger(action: "get", trigger_id: "trig_01Y9HX7i8hedRs28SEBHBJzs")
→ HTTP 200 ✅
``

  1. Verify update works:

``
RemoteTrigger(action: "update", trigger_id: "trig_01Y9HX7i8hedRs28SEBHBJzs", body: {...})
→ HTTP 200 ✅
``

  1. Attempt run:

``
RemoteTrigger(action: "run", trigger_id: "trig_01Y9HX7i8hedRs28SEBHBJzs")
→ HTTP 400 ❌
``

Error Response

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "trigger_id: Field required"
  }
}

Variations Attempted (all fail with same error)

  • body: {} (empty body)
  • body: {"trigger_id": "trig_01Y9HX7i8hedRs28SEBHBJzs"}
  • body: {"id": "trig_01Y9HX7i8hedRs28SEBHBJzs"}

Expected Behavior

According to the tool schema:

  • API endpoint: POST /v1/code/triggers/{trigger_id}/run
  • trigger_id is documented as "Required for get, update, and run"

The run action should work the same as get/update — inserting trigger_id into the URL path.

Suspected Root Cause

The tool implementation likely does not interpolate trigger_id into the URL path for the run action, or the API server expects trigger_id in the request body but the tool only sends it via URL path.

Environment

  • Claude Code CLI
  • macOS (Darwin 23.3.0)
  • Model: claude-opus-4-6

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗