trigger.replay

Coming July 20, 2026

Re-dispatch a failed or DLQ trigger to its handler.

CategoryTrigger
JSON-RPCtools/call
EndpointPOST /mcp

Description

Re-dispatches a trigger that previously failed or landed in the DLQ. The original `Idempotency-Key` is preserved, so if the handler has since recovered and the original POST happened to land (network races), the handler can dedupe. Replay is rate-limited per handler.

Input schema

FieldTypeRequiredDescription
trigger_idstringyesTrigger to replay.

Output shape

typescript
{
  ok: boolean;
  redispatched_at: string;
  attempt: number;
}

Example call

JSON-RPC tools/call request body (omit the JSON-RPC envelope when using an SDK; the SDK adds it for you):

jsontools/call params
{
  "name": "trigger.replay",
  "arguments": { "trigger_id": "trg_01HXP9DLQ" }
}

Example response

Tool results are always wrapped as content[0].text with a stringified JSON body. The shape below is what you get back from JSON.parse(result.content[0].text):

jsonparsed result body
{
  "ok": true,
  "redispatched_at": "2026-05-27T16:02:00Z",
  "attempt": 8
}

Errors this tool can return

CodeMeaning
invalid_argumentsTool input failed Zod validation.
unauthorizedMissing or invalid bearer token.
handler_disabledThe registered handler is disabled (manual disable, repeated failed deliveries, or exceeded DLQ threshold).
quota_exceededPer-minute, daily call, or daily inference budget exceeded.

See the full error catalog for resolution steps on each code, plus the standard transport-layer responses (401, 429).

Notes