
Cloudinary distinguishes starting a different search from continuing the same search. Its Admin API documentation calls for a new Search query object for each distinct query; when following next_cursor, keep the other query parameters unchanged. Mixing those lifecycles can make a campaign's later pages unreliable as a selection record.
Key Takeaways
- A changed campaign filter is a new query, not another page of the previous one.
- A continuation cursor belongs with the query parameters that produced it.
- A paginated search is a retrieval workflow, not an immutable approval archive.
Save the query definition alongside its cursor
Before collecting results, record the expression, resource scope, requested fields, sort policy and page-size setting used by the integration. These are proposed diagnostic fields; use the actual names and types required by the installed SDK.
The Search API guide demonstrates continuing a filtered search with its returned cursor. It also warns that sorting syntax differs among SDKs and REST. Do not copy a request representation from another language merely because the same field name appears in both.
If the request supplies no search parameters, the documented default is the 50 newest assets. Seeing that first response does not establish that every asset in a campaign was examined. Inspect the response and the actual query rather than assuming that a short page represents the entire library.
Separate continuation from a changed filter
Use the Admin API's query-object rules to distinguish these cases:
| Intended action | Query-object policy | Cursor policy |
|---|---|---|
| Continue the same campaign search | Keep its existing definition unchanged | Use the continuation returned for that query |
| Search another campaign or change sorting | Initialize a distinct query object | Begin that new query instead of carrying an old continuation |
The two rules are complementary. Starting a fresh query for a different selection avoids unintentionally carrying builder state, especially sorting. Continuing a current query avoids altering the definition halfway through its pages.
Keep the query plan with the cursor in your application's own state. Do not let a user's filter change update only the visible label while a background iterator continues with the earlier cursor.
Reconcile the collected asset identities
For a proposed small test, choose an authorized campaign whose expected assets you can identify. Collect each returned asset identifier and flag repetitions for investigation. Compare the collected membership against the known test selection; do not merely compare the number of thumbnails on two screens.
Then deliberately start a different query using the supported new-object pattern. Verify that the interface labels, filter definition and returned collection refer to that new selection. This article has not executed either test or established a complete production inventory.
Search indexing is eventually consistent. Do not treat immediate search absence after a modification as proof of deletion, or assume the cursor provides a frozen snapshot while other work changes the library. Observe the actual state and respect the Admin API's usage limits when investigating.
Keep retrieval separate from approval and delivery
Once the intended assets are identified, apply the approved-version record before packaging a client handoff. A search match does not make a version approved. If an offline deliverable is required, verify its actual local files separately from the search response.
Accept the integration when a continuation preserves its query definition, a changed filter starts a distinct search, and collected identities reconcile with the proposed test set. Record any remaining inconsistency instead of compensating by silently dropping repeated results.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- My Archive Shows Every Photo. Why Are Some Unavailable Offline?
Sources and scope
- Cloudinary: Search API method: Documents default first-page results, next_cursor continuation examples, SDK-specific sorting syntax and the rate-limited Admin API.
- Cloudinary Admin API: Search for resources: A distinct query needs a new Search query object. Cursor iteration reuses the query without changing its other parameters. Search indexing is eventually consistent.
Documentation-based integration guidance, not an executed search or a measured completeness test. The campaign and reconciliation examples are proposed. No credentialed API call was made.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.