Use XACKDEL to acknowledge entries in a consumer group and delete them from the stream in one atomic step.
It combines what XACK and XDEL do, which is what you want when a stream serves a single group and processed entries have no reason to stay around. IDS <numids> introduces the list of IDs and the count must match.
The reference policy controls what happens to consumer group references of the deleted entries: KEEPREF, the default, leaves references in other groups' pending lists in place, DELREF removes them everywhere, and ACKED only deletes entries that every group has read and acknowledged, leaving the rest in the stream. The reply holds one status code per requested ID, in the order they were given.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<group> | Yes | No | Consumer group name. |
(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.