sxyazi/yazi · error

Receiver `{receiver}` not found. Check if the receiver is ru

Error message

Receiver `{receiver}` not found. Check if the receiver is running.

What it means

Targeted send validation in `ya pub`: the specified receiver Id is not present in the discovered peer map, meaning no running process matches it. The faulting input is the receiver Id passed on the command line.

Source

Thrown at yazi-cli/src/dds/shot.rs:74

	}

	pub(super) fn ensure_ability(peers: &HashMap<Id, Peer>, kind: &str, receiver: Id) -> Result<()> {
		match (receiver, peers.get(&receiver).map(|p| p.able(kind))) {
			// Send to all receivers
			(Id::ZERO, _) if peers.is_empty() => {
				bail!("No receiver found. Check if any receivers are running.")
			}
			(Id::ZERO, _) if peers.values().all(|p| !p.able(kind)) => {
				bail!("No receiver has the ability to receive `{kind}` messages.")
			}
			(Id::ZERO, _) => Ok(()),

			// Send to a specific receiver
			(_, Some(true)) => Ok(()),
			(_, Some(false)) => {
				bail!("Receiver `{receiver}` does not have the ability to receive `{kind}` messages.")
			}
			(_, None) => bail!("Receiver `{receiver}` not found. Check if the receiver is running."),
		}
	}
}

View on GitHub (pinned to 5f901b886b)

Solutions

1. Start the yazi process you intend to message.
2. Re-check the receiver Id; use `ya pub --list` to see live peers.
3. Restart all ya/yazi processes if they were upgraded, since version mismatches break discovery.

When it happens

Trigger: Thrown at yazi-cli/src/dds/shot.rs:74 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of sxyazi/yazi@5f901b886b (2026-09-02). Data as JSON: /api/errors/538b3d0d975adf6a. Report an issue: GitHub.