Frequently Asked Questions
What happens if my destination server goes down for 3 days?
Bunnylynk holds all incoming events in durable storage. Configured connections will attempt retries following your backoff schedule. Even after max automated retries are reached, events remain stored in the Dead Letter queue for manual bulk replay as soon as your server recovers.
Does Bunnylynk support strict FIFO ordering?
Yes. Connections can be configured with strict FIFO sequencing per partition key (such as body.data.object.customer_id). If an earlier event for that customer fails, Bunnylynk halts subsequent events for that customer until the first event succeeds, preventing out-of-order race conditions.
What is the maximum payload size?
By default, Bunnylynk supports payloads up to 10MB, easily accommodating heavy webhook payloads containing file attachments or full catalog diffs.
How long are event logs retained?
Retention is configurable based on your tier or self-hosted disk policy:
- Free / Hobby: 7 days
- Pro: 30 days
- Enterprise: 90 to 365 days, with automated cold storage archiving to Amazon S3 or Cloudflare R2.
What IP addresses does Bunnylynk use to deliver webhooks?
For self-hosted instances, Bunnylynk uses your own egress IPs. For Bunnylynk Cloud, a dedicated list of static NAT gateway egress IP CIDR blocks is available in your workspace dashboard to whitelist in your firewall.
Can I run Bunnylynk completely offline in local development?
Yes. You can run Bunnylynk with docker compose or using the local workspace dev environment (pnpm dev).