Silent rest
Data source and view queries stop paginating at 10,000 results; start_cursor may now be an opaque string instead of a UUID
What changes
As of April 20, 2026, Query a data source, Create a view query, and Get view query results enforce a max pagination depth of 10,000 results per query, so "fetch all rows" syncs on large databases truncate; the response carries request_status.type "incomplete" (incomplete_reason query_result_limit_reached). As of April 22, 2026, start_cursor accepts opaque strings as well as UUIDs; cursors now embed a session identifier, so code that validates or parses cursors as UUIDs can fail.
Silent: No error. Behavior, results, or cost change quietly.
What to do
Stop assuming exhaustive pagination; check request_status.type for "incomplete" and split the query by filter (e.g. date ranges); treat cursors as opaque strings.
Strings to search for
start_cursornext_cursor/v1/data_sourcesdataSources.querydata_sources.query