← Back to the chapter · Previous detail
Technical detail · CoAP Message Exchanges
CoAP retry times and the final failure deadline
6.10 Interactive: CoAP Retransmission Timeline
A CoAP Confirmable (CON) message requests an acknowledgement (ACK), with bounded retransmission if the ACK is missing.
A retransmission sends the same message again when acknowledgment is missing. CoAP selects one randomized initial wait and doubles it after each retransmission. The retry limit counts retries after the initial send. With an initial two-second wait, random factor one and four retries, sends occur at 0, 2, 6, 14 and 30 seconds. Failure is declared at 62 seconds after the final acknowledgment wait.
A legacy timeline calculator on the CoAP Message Exchanges reference page draws a fresh random multiplier for each retry and omits the final wait from its displayed timeout. That calculator’s explanation records those differences. Do not use its final-send time as the failure deadline or its charge display as a complete battery budget. An unconfirmed exchange also needs the application fallback chosen for its purpose.
The message types workbench shows message roles. The CoAP Message Exchanges reference page retains the original energy and retry calculators, their limitations, detailed examples, and narrated tour for closer inspection.