The PainChek webhook system has a structured retry policy that will attempt to deliver failed messages in a staggered time series.
Note
PainChek registers a successful receipt by HTTP response codes in the 2xx and 3xx range.
Any response in the 4xx or 5xx range are considered failures.
The table below outlines the retry attempt stages for outgoing webhook messages.
|
Retry # |
Time since last attempt |
Total time from original attempt |
|---|---|---|
|
1 |
1m |
1m |
|
2 |
4m |
5m |
|
3 |
10m |
15m |
|
4 |
45m |
1h |
|
5 |
2h |
3h |
|
6 |
3h |
6h |
|
7 |
6h |
12h |
|
8 |
12h |
24h |
|
9 |
24h |
48h |
|
10 |
24h |
72h |
Note
-
After the 11th attempt to send the message (i.e. the original attempt plus the 10 retries over a 72 hour period), we abandon attempts to send the event. It will be available for manual resend via the PainChek Web admin portal (WAP).
-
Manually resending the message will not reintroduce the message into the retry policy. If a manual resend fails, the only way to resend it is to do it manually again.
-
The above retry policy applies to Production systems. Test systems - e.g. the User Acceptance Testing system - use a more aggressive retry policy. Each of the 10 retries occurs after a 5 second delay.