2026.10.31 — 2026-10-07

Fixed

• Report an unreadable node instead of a missing queue (86ec3343)

  Sending to, browsing or reading a queue that the scrape has not reached yet asks each node live. When a node could not be read, because Studio was holding calls to it back under the management-call rate or it did not answer, Studio treated that as the queue not being there and answered 404 "queue … does not exist". It now answers with the node's own failure (503, held back or unreachable), so a client retries instead of giving up on a queue that exists. A queue that no readable node has is still a 404.