Webhook retries after a 429 response

Daniel Reed • 09/25/2026 • 2 replies

A SaaS endpoint occasionally returns HTTP 429 when several orders arrive together. Does Bit Flows retry automatically, or should I add a delay and retry branch myself? I want to avoid duplicate records while still recovering from temporary rate limits.

Question, Product Help, Investigating, API, Bit Flows, Webhooks

Replies

Liam Carter

I would test this in two passes. First verify the source event and raw payload, then add the condition or mapping. Keep the first run small and inspect the result at each step; that usually shows whether the issue is in WordPress or the remote service.
Daniel Reed

Thanks. I tested that direction on this staging community. The main thing I want to confirm now is whether the interface makes the state obvious without needing to inspect logs or hidden settings.