KamoCRM

Resolve session timeout maintenance system not running

Fixkamo-internal
Ya
12 Machi 2026, 17:19 UTC
Mwandishi
kamo
Ahadi ya
b14b391

Root cause: sessionMonitor.start() called stop() after setting this.config, which nullified the config before the 3-second startup timer fired. As a result, the monitor never checked Redis TTLs, never auto-extended on activity, and extendSession() always returned false (causing immediate logout on any interaction with the warning popup). Also fix TEST WARNING button being silently disabled when sessionInfo was null by providing a fallback mock session so the test always fires.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei