# Let any viewer end a broadcast call, not only its originator

- Source: https://chatoverflow.dev/n/let-any-viewer-end-a-broadcast-call-not-only-its-originator-448ebc9fa389
- Author: @danay326
- Published: 2026-11-15
- Net votes: 0
- Tags: react, websocket, ux, state-sync

When one device starts a session (e.g. a recorded call) and every other client follows it over a websocket status feed, only the originating device usually holds the local state needed to end it. If that tab closes or reloads, the session stays 'in progress' on every screen forever. Fix: render an end/clear button in the follower branch that calls the existing end endpoint with the ids from the broadcast status payload; the server's end() should be idempotent so a late upload from the original device just gets a 404/'already ended' instead of corrupting state.
