Loading

Data 360: Query Service v2 - nextBatchId Format Change for Connect API and Direct API

Publish Date: May 20, 2026
Description

Salesforce is updating the format and length of the nextBatchId returned by Data 360 Query Service v2 for both the Connect API and Direct API. Client applications that parse or depend on the structure of the current UUID-based nextBatchId must be updated to treat this value as an opaque string to avoid failures when retrieving subsequent data batches.

Data 360 Query Service v2 supports paginated data retrieval via two endpoints:

When a customer initiates a POST call to retrieve data and additional chunks are available, the API response includes a nextBatchId. This ID is then passed in a follow-up GET call to retrieve the subsequent data batch.

What is Changing?
Currently, the nextBatchId is a UUID (Universally Unique Identifier). With this update, the nextBatchId format changes to a combination of the query ID and chunk ID, which increases its length. The new format resembles a structure like query-id_chunkCount.

Previous format : 2c55b4dc-df7e-e1bd-d346-e1395085d5d9

Example of the New Format
MTAuMjIuNDguODY6NzQ4NA_2c55b4dc-df7e-e1bd-d346-e1395085d5d9_1 (for the 1st chunk)

Why is Salesforce Making This Change?
The current implementation uses a distributed cache to store batch details against the nextBatchId. This adds significant operational overhead and Cost to Serve. By updating the nextBatchId format, Salesforce moves toward a stateless parsing model, which eliminates the cache from this flow.

Resolution

To avoid disruption to data retrieval, customers must review and update their client applications before this change takes effect.

Required Actions

  1. Treat nextBatchId as an opaque string. Do not parse, inspect, or make assumptions about the format, length, or structure of the nextBatchId value.
  2. Review your code for any existing logic that depends on:
    1. The specific format or length of the nextBatchId
    2. The previous UUID structure of the nextBatchId
  3. Remove any such dependencies. Applications that rely on the format or structure of the nextBatchId are expected to break when this change is released.

 

What Happens If No Action Is Taken?

If customers do not take action, they will experience failures when attempting to retrieve subsequent data chunks, as their applications will fail to resolve the new nextBatchId structure. This will result in an inability to fetch complete datasets, leading to data discrepancies.

Note: Only applications with custom logic that reads or parses the nextBatchId value are affected. If your application already treats nextBatchId as an opaque string, no changes are required.

Knowledge Article Number

005384667

 
Loading
Salesforce Help | Article