Retry Policy
Sensos implements a retry policy for data delivery to ensure successful transmission of data, even in cases of temporary communication failures. This policy governs the intervals at which retry attempts are made if the initial delivery attempt fails. The retry policy is designed to progressively increase the delay between attempts, minimizing the risk of overwhelming the target system while maintaining data integrity.
Retry Policy Overview
When an attempt to deliver data fails, the system will retry according to the exponential backoff algorithm, increasing the delay between successive attempts. The formula used to calculate the delay is:
Delay = 2^(number of retries)* 30 seconds
This results in progressively longer delays between retry attempts. The retry mechanism will continue until the data is successfully delivered or the maximum number of attempts is reached.
Retry Table
The following table outlines the delay intervals for each retry attempt, up to the 13th attempt:
| Attempt Number | Retry Number | Delay (seconds) | Accumulated Delay (seconds) |
|---|---|---|---|
| 1 | 0 | 0 | 0 (0 minutes) |
| 2 | 1 | 30 | 30 (0.5 minutes) |
| 3 | 2 | 60 | 90 (1.5 minutes) |
| 4 | 3 | 120 | 210 (3.5 minutes) |
| 5 | 4 | 240 | 450 (7.5 minutes) |
| 6 | 5 | 480 | 930 (15.5 minutes) |
| 7 | 6 | 960 | 1890 (31.5 minutes) |
| 8 | 7 | 1920 | 3810 (1.06 hours) |
| 9 | 8 | 3840 | 7650 (2.13 hours) |
| 10 | 9 | 7680 | 15330 (4.26 hours) |
| 11 | 10 | 15360 | 30690 (8.52 hours) |
| 12 | 11 | 30720 | 61410 (17.06 hours) |
| 13 | 12 | 61440 | 122850 (34.13 hours) |
Updated 2 months ago