BLPOP, BRPOP, and blocking XREAD are not supported over Upstash REST: poll or use RESP
HTTP 400 or unsupported-command errors calling BLPOP, BRPOP, BRPOPLPUSH, BZPOPMAX, BZPOPMIN, or blocking XREAD over Upstash REST. Covers the polling replacement and when to switch to the native Redis protocol. Not for non-blocking commands or native-protocol connections.
TL;DR: Blocking Redis commands need a held connection, and REST has no connection to hold, so BLPOP, BRPOP, BRPOPLPUSH, BZPOPMAX, BZPOPMIN, and XREAD/XREADGROUP with BLOCK fail over Upstash REST with an HTTP 400 or unsupported-command error. Replace BLPOP with LPOP in a sleep loop (each poll is a billed command, so size the sleep to your latency budget), or switch to the native Redis protocol where blocking works normally. For queue consumers, the protocol path is the right call.
What you see:
HTTP 400, or an unsupported-command error, when calling BLPOP, BRPOP,
BRPOPLPUSH, BZPOPMAX, BZPOPMIN, or XREAD/XREADGROUP with BLOCK.Steps:
- Decide which path fits. Polling over REST is fine for low-frequency consumers; anything queue-like wants the native protocol. Success: you picked one deliberately.
- Polling path: replace BLPOP with LPOP in a loop that sleeps briefly between attempts. Success: the consumer picks up a pushed item within the expected poll window.
- Protocol path: connect over RESP with a persistent connection and keep using blocking commands unchanged. Success: BLPOP behaves exactly like self-hosted Redis.
- Streams over REST: use non-blocking XREAD (no BLOCK argument). Success: reads work without the BLOCK flag.
When to use: blocking commands fail over Upstash REST with 400/unsupported-command.
When not to use: you control the client and can open a RESP connection (just use the protocol), or the command is non-blocking (it works fine over REST already).
Compatibility: Upstash Redis REST API, any HTTP client. Native protocol path needs a RESP-capable client.
Variants:
- upstash blpop not supported
- upstash rest blocking xread
- upstash redis blocking commands rest
Root cause: blocking commands hold a connection open waiting for data. REST is request/response per call, so there is no connection to hold. The compatibility table marks all of these unsupported by design, not by bug.
Edge cases:
- Cost: polling every 100ms is 864K commands a day per consumer. At pay-as-you-go rates that is real money. Prefer the protocol path for blocking-style consumers, or lengthen the poll interval and accept the latency.
- Verify end to end: RPUSH a test item and watch the consumer pick it up.