Checking Delivery Status
Understand event delivery statuses and what to do when deliveries fail.
Delivery Statuses
| Status | Description |
|---|---|
| Delivered | Event accepted by the destination API (2xx response) |
| Pending | Event queued for delivery, not yet sent |
| Retrying | Delivery failed, automatically retrying (5xx or network error) |
| Failed | Delivery permanently failed after all retry attempts |
| Skipped | Event type not configured for this destination |
Common Error Codes
| Code | Meaning | Action |
|---|---|---|
| 400 | Bad request — invalid event data | Check event format and required fields |
| 401/403 | Authentication failure | Verify API key or access token |
| 429 | Rate limited | MRKT Mesh auto-retries with backoff |
| 500+ | Destination server error | MRKT Mesh auto-retries up to 3 times |
Retry Behavior
When a delivery fails with a retryable error (5xx, 429, or network error), MRKT Mesh automatically retries with exponential backoff. The default retry schedule is:
- 1st retry: 30 seconds
- 2nd retry: 2 minutes
- 3rd retry: 10 minutes
After 3 failed attempts, the delivery is marked as permanently failed. If a destination has a high failure rate, MRKT Mesh activates a circuit breaker to prevent overwhelming the API.
Viewing Delivery Details
Click any event in Monitoring → Real-Time to see per-destination delivery details including status code, response time, and error message.