Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

Merge remote-tracking branch 'origin/main' into fix/session-reconnect-policy-cap

Yudhi Armyndharis765d7f1ceb98
diff --cc CHANGELOG.md
index ba50a2d67,373b3e0a6..797dd26ce
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -13,7 -13,8 +13,9 @@@ and this project adheres to [Semantic V
### Fixed
+ - A session whose automatic reconnect fails to relaunch the engine (a network, DNS or browser launch error) keeps retrying with backoff instead of stopping in `failed` until restarted by hand; an authentication failure or a stale browser profile still ends in `failed` ([#1580](https://github.com/rmyndharis/OpenWA/issues/1580)).
+ - A session that runs out of reconnect attempts fires the `session:error` plugin hook when it lands in `failed`.
+- An explicit `maxReconnectAttempts` is honoured and the reconnect delay is capped at 5 minutes; the budget used to restart once the backoff passed 5 minutes, so the limit was never reached and the documented 1-hour cap never applied.
## [0.23.5] - 2026-09-14