Docs

Retries

Retries help a connection recover from temporary destination failures without losing accepted webhook traffic.

Use them for transient 5xx responses, networking failures, and short destination maintenance windows.

Retry Rule

A retry rule belongs to a connection. It decides how many times FastHook should try a failed delivery and how much time should pass between attempts.

  • Use exponential backoff for destinations that need breathing room.
  • Keep retry counts deliberate so a broken downstream service does not create noisy traffic.
  • Match status-code rules to the failure modes your destination can recover from.

Manual Replay

For incident recovery, failed events can be replayed after the destination is fixed. Replays are useful when retries have already been exhausted.

Idempotency

Any system that receives webhook retries should handle duplicate deliveries. Store provider event ids or FastHook event ids and treat repeated deliveries as safe no-ops when the work has already completed.

Next