Hi GP, thank you for the detailed follow-up! Let’s dive deeper into the possible areas contributing to the issue:
For WebSocket and Real-time Updates - You can check WebSocket stability by looking for any WebSocket errors in your browser’s developer tools (on desktop) or through network debugging tools on mobile. Additionally, inspect server logs for any WebSocket disconnection or reconnection messages that might indicate instability.
For Push Notifications - While push notifications are generally for alerts, the push proxy could potentially affect status updates if there’s a misconfiguration. Make sure that your server’s push notification settings, specifically around user activity and availability, are correctly configured.
For Session Management Clearance - You can go to the System Console > Users and manually revoke sessions across platforms, ensuring that a stale session isn’t causing the status desync. Additionally, check the “Session Idle Timeout” in System Console > Environment > Session Lengths to ensure sessions are being managed as expected.
For Logs/Monitoring - For logs, you might want to search for status_update events, as they can provide insights into any failures or delays in updating user status. Also, reviewing your server performance logs, particularly related to load balancing and connection timeouts, might reveal bottlenecks impacting the status syncing.
Lastly, you may want to verify if your server is behind any proxies or load balancers, as these can sometimes interfere with real-time updates or WebSocket connections.
Please let me know if this helps or if you need any further clarification!