Errors and retries
What WRMS Pro treats as a successful webhook delivery, how failed deliveries are retried, and when a webhook is paused automatically.
Success and failure
| Your endpoint… | Result |
|---|---|
Responds with any 2xx status within 10 seconds | Success |
Responds with 3xx | Failure — redirects are not followed |
Responds with 4xx or 5xx | Failure |
| Takes longer than 10 seconds, or cannot be reached | Failure |
The first 4 KB of your response is kept with the delivery record to help you debug.
Retries
A failed delivery is retried automatically, up to 5 attempts in total, waiting longer each time:
| After attempt | Next try in about |
|---|---|
| 1 | 1 minute |
| 2 | 5 minutes |
| 3 | 30 minutes |
| 4 | 2 hours |
Each retry sends the same body with a fresh signature, and X-WRMS-Attempt goes up by one. After the fifth failure the delivery is marked failed. You can retry it by hand from Deliveries in Settings → Webhooks.
Automatic pause
If a webhook fails 20 times in a row, WRMS Pro turns it off so it stops sending to a broken endpoint. A successful delivery resets the count. After fixing your endpoint, turn the webhook back on in Settings → Webhooks and select Send test.
Ordering and duplicates
- Deliveries can arrive out of order, especially when retries are involved. Use
createdAtto order events, and re-read state rather than trusting the order of arrival. - The same delivery can arrive more than once. Skip deliveries whose
X-WRMS-DeliveryID you have already processed.
Troubleshooting a failing webhook
- Open Deliveries for the webhook and look at the status code and response.
- Check your endpoint is reachable from the internet over HTTPS and does not redirect.
- Check signature verification uses the current secret and the raw body.
- Respond before doing slow work.
- Select Send test and watch your endpoint's logs.
Still need help?
Email support@wrmspro.com or use the contact form. Signed-in users can also send a request from Settings → Support.