Inbound Retry Behavior

Why You Would Use This

Inbound retry behavior applies after a webhook is accepted at ingest. If forwarding from HookBridge to your destination fails, HookBridge automatically retries using exponential backoff so temporary downstream issues do not immediately become data loss.

If the receiver returns Retry-After, HookBridge honors it as a minimum retry delay (with safety caps).

Status Lifecycle

Forwarding status flow:

• queued
• delivering
• succeeded
• pending_retry
• failed_permanent

pending_retry means automatic retries are still in progress.
failed_permanent means retries stopped and manual recovery is needed.

Console Workflow

1. Open Messages and switch to inbound direction.
2. Filter by pending_retry to watch active retry backlog.
3. Filter by failed_permanent to identify messages requiring intervention.
4. Replay single failed messages or use Replay All after downstream recovery.
5. Pause/resume inbound endpoints when you need to control intake during maintenance.

API Workflow

API reference:

• Replay inbound message
• Replay all inbound messages
• Pause inbound endpoint
• Resume inbound endpoint

# Replay one inbound message
curl -X POST https://api.hookbridge.io/v1/inbound-messages/YOUR_INBOUND_MESSAGE_ID/replay \
  -H "Authorization: Bearer YOUR_API_KEY"

# Replay many by status
curl -X POST "https://api.hookbridge.io/v1/inbound-messages/replay-all?status=failed_permanent&limit=100" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Pause endpoint
curl -X POST https://api.hookbridge.io/v1/inbound-endpoints/YOUR_INBOUND_ENDPOINT_ID/pause \
  -H "Authorization: Bearer YOUR_API_KEY"

# Resume endpoint
curl -X POST https://api.hookbridge.io/v1/inbound-endpoints/YOUR_INBOUND_ENDPOINT_ID/resume \
  -H "Authorization: Bearer YOUR_API_KEY"

Operational Tips

• Let automatic retries work before triggering manual replay.
• Use replay-all only after confirming the underlying issue is fixed.
• Prioritize recovery by endpoint/business criticality.