fix(commissioner): extend operational connect timeout to 4m15s (#3674)

Apollon77 · web-flow · commit 8fd498888327 · 2026-04-29T11:29:41.000+02:00
* fix(commissioner): extend operational connect timeout to 4m15s

Several commissioning steps allow up to ~2 minute server-side delays.
The previous 4 minute CASE connect timeout left too little headroom in
back-to-back delay scenarios. Bumping to 255 seconds keeps us safely
inside the 5 minute failsafe re-arm and matches observed worst-case
peer behavior. Failsafe reset on operational connect failure already
fires through the existing CommissioningError catch path.

* docs(commissioner): note rationale for 4m15s connect timeout

Two ~2-minute server-side retry windows fit within 4m15s before we
abort the operational connect.
diff --git a/packages/protocol/src/peer/ControllerCommissioner.ts b/packages/protocol/src/peer/ControllerCommissioner.ts
@@ -40,7 +40,6 @@ import {
     Logger,
     MaybePromise,
     Millis,
-    Minutes,
     NoResponseTimeoutError,
     Seconds,
     ServerAddress,
@@ -583,7 +582,8 @@ export class ControllerCommissioner {
                 const peer = this.#context.peers.for(address);
                 peer.descriptor.discoveryData = discoveryData;
                 await peer.connect({
-                    connectionTimeout: Minutes(4),
+                    // 4m15s allows two ~2-minute server-side retry windows to complete before we abort.
+                    connectionTimeout: Seconds(255),
                     timing: caseConnectionTiming,
 
                     handleError: error => {
