Winflector Session Disconnects and Idle Timeout Settings Explained
A user loses Wi-Fi for ten seconds — and either returns to their work untouched, or finds their session gone and a licence seat still occupied. Both outcomes come from session settings. Understand them once and tune them deliberately.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the full video — Winflector installation and app publishing, shown live step by step
Three different events get called a disconnect, and they have different fixes. A network drop breaks the connection but the session can survive on the server. A session close ends the user's work and frees the licence. An idle timeout is the server deciding a forgotten session should end. Mixing them up is why users lose unsaved work while other offices leak licence seats all day.
Winflector server — sessions in three different states
👤 owner — Billing App — idle for hours, still holding a licence seatIdle
☝️ Disconnected is not the same as closed — a kept session lets the user return to their work, an idle one silently eats a licence
1
Turn On Client Auto-Reconnect
The native client supports automatic reconnection: the option is -RCNTM=seconds on the client command line or the matching setting in the client, which makes the client keep retrying for that long after a drop
Give it a sensible window — long enough to survive a Wi-Fi hiccup or a router restart (a few minutes), not so long that a dead connection retries all day
Browser (HTML5) users simply log in again after a drop; if the server kept their session, they return to the same open application
2
Keep Disconnected Sessions Long Enough
On the server, set how long a disconnected session is kept before it is closed. Too short, and a two-minute network failure throws away the user's unsaved voucher
For accounting and billing work, a generous keep time (tens of minutes) is usually the right trade — the seat stays occupied a bit longer, but nobody loses real work
For casual, view-only use, a short keep time returns seats to the pool faster. Decide per office, not by default
3
Use Idle Timeouts to Free Stuck Seats
An idle timeout closes sessions that have had no activity for the set period — this is what stops a forgotten Friday-evening session from holding a licence seat all weekend
Warn users before enabling a short idle timeout: a session closed by the server ends the application, and unsaved entries in it can be lost
Balance it: long enough that reading a long report is not punished, short enough that seats recycle during the working day
4
Clear a Stuck Session as Admin
From the server console, look at the session list: a user who left long ago but still shows connected is holding a seat and may also be locking records in the application
Confirm with the user (a quick call) that they are really out, then close that session from the server side
If stuck sessions happen daily, the cause is behaviour or settings — users closing the laptop lid instead of the app, or no idle timeout at all. Fix the cause, not just the symptom
🔴 Every timeout is a trade. Short timeouts free licences quickly but can destroy unsaved work; long ones protect work but waste seats. There is no universally correct number — there is only the number that fits how your office actually works. Set it deliberately and tell your users what you set.
🎥 Watch the Complete Setup in the Full Video
The full video shows a correct Winflector installation — session behaviour makes sense once you have seen the server console working as shown there.
The user closed the laptop lid and now the licence seat is stuck. What happened?
Closing the lid usually suspends the connection without closing the session, so the server keeps the session — and its licence seat — alive. The session returns when the user reconnects, or an admin can close it from the server console after confirming the user is done.
Will a user lose unsaved work if the internet drops?
Not automatically. If the server is set to keep disconnected sessions and the user reconnects within that window (the native client can reconnect automatically with the -RCNTM option), they return to the same session with work intact. Work is only at risk when the session itself is closed.
Why do sessions close even though the user was still logged in?
An idle timeout on the server closes sessions with no activity for the configured period, precisely to free licence seats. If it triggers during legitimate quiet work like reading reports, lengthen it — and warn users that truly idle sessions will be ended.
This guide is based on the Technical Anshu Winflector setup video • Stuck on any step? Ask in the video comments — help is available there 🙏