## TL;DR

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.

## Steps

1. 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.

2. 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.

## When to use

You are seeing this: 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... Use this skill when you run into "Deactivated Stream Chat user still receiving messages".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: stream-chat-js 1.7.2. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.