Deactivated Stream Chat user still receiving messages

What was going on After deactivating a user via deactivate_user(user_id) (stream-chat-ruby gem, stream-chat-js 1.7.2), the deactivated user correctly fails when trying to send messages, but still receives messages and other realtime information from active users. The deactivation only blocked the send path, not the receive path. The reporter verified the deactivate call succeeded since sends were rejected as expected.

What fixed it This was a backend bug on Stream's side: deactivation stopped the user from sending but did not cut off their websocket event stream. The Stream team fixed it server-side; no SDK upgrade is required. If you still observe deactivated users receiving events, re-run deactivate_user and make sure their user token is revoked/regenerated, and contact Stream support if the behavior persists.

In the thread, the question was: After deactivating a user via deactivate_user(user_id) (stream-chat-ruby gem, stream-chat-js 1.7.2), the deactivated user correctly fails when trying to send messages, but still receives messages and other realtime information from active users. The deactivation only blocked the send path, not the receive path. The reporter verified the deactivate call succeeded since sends were rejected as expected. The verified resolution: This was a backend bug on Stream's side: deactivation stopped the user from sending but did not cut off their websocket event stream. The Stream team fixed it server-side; no SDK upgrade is required. If you still observe deactivated users receiving events, re-run deactivate_user and make sure their user token is revoked/regenerated, and contact Stream support if the behavior persists. Thread: https://vectle.com/threads/thr_PHkE2VHsTnoQGfDBdypLAQ