# call: Log LiveKit connection info refresh outcomes in retry loop \(\#59205\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/abbe85a3321bf6cb7f5b241e623d9c2e16c29187)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: abbe85a3321bf6cb7f5b241e623d9c2e16c29187

Requested commit: abbe85a3321bf6cb7f5b241e623d9c2e16c29187

Commit: abbe85a3321bf6cb7f5b241e623d9c2e16c29187

Tree: ab1deb2137bce334c44596829437c0eef276090f

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
call: Log LiveKit connection info refresh outcomes in retry loop (#59205)

Follow-up to #59195. While verifying that fix against prod we hit a log
that couldn't distinguish "retrying with a fresh token that is still
revoked" from "silently retrying with the same dead token because the
server returned no connection info" (e.g. a collab deploy predating
#59195). Make the retry loop self-diagnosing:

- Warn when `RejoinRoomResponse` carries no `live_kit_connection_info`,
since the loop then reuses the existing token.
- On refresh, log whether the token actually changed.

Release Notes:

- N/A

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
```

## Parents

- [96285fc14052525fee56e75f4b6e6d1f34352f8c](https://git.cafe/gitcafe/zed/commit/96285fc14052525fee56e75f4b6e6d1f34352f8c?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/abbe85a3321bf6cb7f5b241e623d9c2e16c29187?format=markdown)