Edit history

The Fluxer Gateway does not send SESSIONS_REPLACE when opening another Fluxer client has not been edited, so there are no earlier versions.

Current version | Original by Jonas
Show

The Fluxer Gateway does not send SESSIONS_REPLACE when opening another Fluxer client

Observed behaviour

I connected to the Gateway and dumped all Gateway events. I saw a SESSIONS_REPLACE event, when I closed my Fluxer desktop client, but I didn't get one, when I opened the client.

Reproduction steps

Build information

Stable Desktop 2026.1004.10845, Web 2026.1008.22643, Linux 7.2.8-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

API

Evidence

Reproduction example output:
READY saved to ready.json
Session ID: ...
Sequence: 1
Dispatch: SESSIONS_REPLACE (seq=2): {"d": [{"afk": false, "mobile": false, "session_id": "all", "status": "offline"}, {"afk": false, "mobile": false, "session_id": "...", "status": "offline"}], "op": 0, "s": 2, "t": "SESSIONS_REPLACE"}
Dispatch: SESSIONS_REPLACE (seq=3): {"d": [{"afk": false, "mobile": false, "session_id": "all", "status": "offline"}, {"afk": false, "mobile": false, "session_id": "...", "status": "offline"}], "op": 0, "s": 3, "t": "SESSIONS_REPLACE"}
The desktop Fluxer client was opened while the script was started. Then it was closed (first SESSIONS_REPLACE event), then it was opened again (no event), then it was closed again (second SESSIONS_REPLACE event).