Outemit
Start free
Outemit

Debug deliveries

Self-serve delivery debugging is a core product surface. Use the Deliveries table and detail drawer before opening a support ticket.

Open the delivery

  1. 1

    Filter to the failure

    Dashboard → Deliveries. Use Failed 24h, status filters, or search by event type / endpoint URL / id. Filtered empty is not the same as a first-run empty workspace.

  2. 2

    Open the detail

    Click the row. You get attempt timeline, request headers/body, response status/body, next retry time, and actions.

  3. 3

    Fix the receiver, then choose an action

    Confirm whether the bug is on the receiver (handler crash, auth, schema) or the URL (DNS, TLS, firewall). Then Retry or Replay deliberately.

What to read

  • HTTP status + latency – quick health signal
  • Response body – the receiver's error message (often the fix)
  • Attempt number + trigger – auto vs manual
  • Next retry – when Outemit will try again
  • Copy as cURL – reproduce outside the dashboard

Status code guide

  • 2xx – success; delivery complete
  • 408 / 429 / 5xx / network errors – retryable; exponential backoff
  • Other 4xx (not 429) – usually not retried forever; fix the receiver or signature verify

Retry vs Replay

  • Retry – same delivery, same endpoint, new attempt. API POST /api/v1/deliveries/:id/retry
  • Replay – message re-enters the pipeline; new deliveries for current subscriptions. API POST /api/v1/messages/:id/replay

Deep dive: Core concepts.

Loading diagram...

Auto-disable

After N consecutive failures, Outemit can disable the endpoint and surface an Issue. Fix the receiver, re-enable the endpoint, then Retry failed deliveries or Replay recent messages as needed.