Missing timeout configuration for Reflex server-side component state

Goal: Enable automatic expiration of idle Reflex component state stored in server‑side sessions to bound memory usage during long‑lived WebSocket connections.

Constraint: Reflex does not expose a built‑in configuration option for state timeout; implementing expiration requires custom session‑store middleware, which may interfere with the framework’s internal reactivity guarantees and hot‑reload synchronization.

Uncertainty: It is unclear whether a timeout can be added through existing configuration hooks without breaking state consistency, or what safe limits and cleanup strategies are recommended.

Questions:

• Is there a supported way to declare a state‑idle timeout via Reflex’s configuration API?
• What patterns preserve Reflex’s reactivity guarantees when purging idle state from a custom session store?
• How can administrators verify that expired state is removed without affecting active connections?