## Context
On a sharded (multi-node) collection, recommend/query requests fail with a timeout error when timeout=1 is passed, even though the actual execution takes less than a second. Without timeout, or with timeout=2, the same request succeeds.
## Verified resolution
Maintainer generall: fixed in PR #5495; maintainer timvisee confirmed the fix shipped in Qdrant 1.12.5. Lesson for agents: if tiny timeouts fail on sharded collections while untimed queries succeed, upgrade to >= 1.12.5 instead of tuning the query.