DEVELOPER GUIDEHow to reconnect a dropped Linked Devices session
Design a visible recovery path for disconnected sessions instead of silently losing queued messages.
Developer guide for reconnecting a linked device. Validate the behavior in your own stack before production rollout.The problem
Model connected, degraded, disconnected, reconnecting and requires_repair states explicitly.
Model every session state explicitly instead of a single online flag.Design the boundary
Pause new sends, alert an authorized operator and expose a short-lived QR pairing flow scoped to the workspace.
Hold messages, alert a person, re-pair, and only then resume.Process the interaction
Resume queued messages only after the provider confirms a healthy session; preserve idempotency keys.
Measure the outcome
Measure disconnect frequency, time to re-pair and messages held during recovery.
BUILD IT SAFELYMake the failure path part of the design.
Reliable messaging is an operational system, not only an API call.
Start free 