Use XDELEX to delete entries from a stream with control over what happens to consumer group references.
IDS <numids> introduces the list of IDs and the count must match. The policy decides how consumer groups are affected: KEEPREF, the default, deletes the entries but leaves them in the pending entries lists of the groups that had received them, DELREF removes those references as well, and ACKED only deletes entries that every group has read and acknowledged, leaving the others in place.
That last policy is what makes the command useful as a safe cleanup step: it removes exactly the entries nobody still owes work on. The reply holds one status code per requested ID, in the order they were given. Where XDEL always behaves like KEEPREF, XDELEX is its explicit form.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
(KEEPREF | DELREF | ACKED) | No | No | What happens to consumer-group references of the deleted entries: KEEPREF (the default) leaves them in place, DELREF removes them from every group's pending list, and ACKED only removes entries that every group has read and acknowledged. |
IDS <numids> <id> [<id> ...] | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Array of integer status codes, one per ID |
| RESP3 | Array of integer status codes, one per ID |
Status codes#
| Code | Meaning |
|---|---|
1 | The entry was deleted. |
-1 | No entry with that ID exists in the stream. |
2 | The entry exists but was not deleted, because ACKED was requested and some group has not acknowledged it. |
The codes come back in the order the IDs were given. An ID listed more than once is processed once, and every occurrence of it carries the same code.
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.