# error.ControlModeErrorKind.Unread

- **Module:** error.ControlModeErrorKind
- **Package:** libtmux
- **Language:** Rust
- **Kind:** constant
- **Source:** https://github.com/libtmux/libtmux-rs/blob/8a648c0894dfffc9303583f753b6c8ae01f2fe76/crates/libtmux/src/error.rs#L149
- **Page:** https://libtmux.org/reference/rs/error-controlmodeerrorkind-unread/

The caller stopped reading events, so the connection could not reach this command's reply.

A reply arrives on the connection the events arrive on. The connection
holds what a caller has not taken and keeps reading while a reply is
outstanding, but not without limit, and past that limit it stops rather
than growing. The events remain held and the connection carries on once
they are taken.

A new request can be refused before it is written, but an already-live
request gets the same error after crossing the write boundary. This
kind therefore does not prove that a mutation is safe to replay. Drain
the events before sending more work, or watch from a task of its own so
the two never contend.