# agent: Lower "no thread found" logging level to debug \(\#31972\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 854076f96dfa4936b345c44c951e769e5d497abf

Requested commit: 854076f96dfa4936b345c44c951e769e5d497abf

Commit: 854076f96dfa4936b345c44c951e769e5d497abf

Tree: 5e20f8d5f7a4eb53876e9a36c941d4763a89fc60

Author: Oleksiy Syvokon

Committer: GitHub

## Message

```
agent: Lower "no thread found" logging level to debug (#31972)

This code path is not really an error, as it can happen due to normal,
albeit uncommon, actions. Like, for example, this scenario:

1. Create a thread X in Zed instance A
2. Open Zed instance B
3. Delete the thread X in instance A
4. Close instance B. This will write non-existing thread id X to
`agent-navigation-history.json`
5. Open Zed instance C. It won't be able to load the thread X.

Another way to get into this state is by running Zed with LMDB and
SQLite thread storages side-by-side.

In any case, this is not severe enough for an error.

Closes #ISSUE

Release Notes:

- N/A
```

## Parents

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

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