Skip to main content
Use SSCAN to iterate the members of a set in batches instead of reading them all at once. Each call takes a cursor and returns the next cursor together with a batch of members. Start at cursor 0 and keep calling with the cursor from the previous reply until the server returns 0, which ends the iteration. MATCH filters members with a glob-style pattern and COUNT hints at how much work each call should do. Filtering happens after a batch is read, so a call can come back empty while the cursor is still non-zero: only the cursor tells you the iteration is over. Members present for the whole iteration are returned at least once, while those added or removed while it runs may or may not appear, and a member can be returned more than once, so keep the processing idempotent.

Syntax

Arguments

Important points

  • This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
  • The cursor is opaque. Start with 0 and continue until the server returns cursor 0; a single iteration may return no elements.

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.
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.