Mercur
Try live

Replay a stored request

Retry in console request history re-sends a stored HTTP request through the same endpoint. Use it after you change a handler, so you can test against the payload that already arrived instead of waiting for the provider to deliver again.

Replay is an explicit action. Mercur does not queue or replay requests that arrived while the agent was disconnected.

What Retry needs

All of these must be true:

  1. A stored HTTP request. The endpoint recorded the original call — Log mode, or Proxy mode with full traffic capture. WebSocket and TCP have no HTTP request log, so they cannot be replayed this way.
  2. Proxy mode. Retry forwards through the endpoint. Log-only mode records and answers 204 without forwarding; Retry then fails with 409 (PROXY_MODE_REQUIRED). Start the endpoint in Proxy or Log and Proxy.
  3. A connected agent. The macOS app or the npm CLI must be forwarding. If the agent is offline, Retry fails with 409 (AGENT_OFFLINE). The public URL answers 503 until the agent reconnects — see troubleshooting.
  4. A complete payload. Bodies omitted because they exceeded the capture preview cannot be rebuilt. Retry then fails with 422 (PAYLOAD_OMITTED). See security and data retention.

How to run it

Open the endpoint in the console, select a row in request history, and press Retry. The relay rebuilds method, path, query, headers, and body from the stored log and sends that request through the live endpoint to your local process.

Plan limits still apply: stored-request caps drop the oldest rows, and everything is deleted after the retention window regardless.

Related