Short answer: treat connection token rotation as a recoverable state transition, not a timer callback; keep quiz authority on the server, give every logical session and answer a stable identifier, and use presence as evidence to reconcile after reconnects rather than as proof that a player submitted an answer.
The page arrives as “players disappeared during question 7.” On-call sees a dip in connected participants, a burst of reconnects, and clients asking for fresh authorization at roughly the same time. The tempting action is to extend token lifetime. Don't start there. First determine whether game state was lost, duplicated, or merely hidden while the connection changed.
For a multiplayer quiz with a collaborative host editor, presence accuracy matters in two places: players need a credible roster, while editors need cursor state that doesn't linger after a connection expires. Those are visibility concerns.…