Adobe Experience Cloud
DA Live migration needs a query contract for Content Fragments
Map GraphQL filters and persisted queries before moving AEM Content Fragment consumers to DA Live.
October 31, 2026
A content move can look finished in the authoring interface while consuming applications still cannot retrieve the right record. A new Adobe DA Live issue asks for GraphQL-equivalent querying and filtering of structured content, or a documented alternative. The issue identifies AEM Content Fragment consumers using GraphQL and persisted queries as the affected group. It is an open capability request, not proof that every DA Live use case lacks retrieval.
Inventory the retrieval contract
List each consuming channel, its persisted query, variables, filters, sort order, locale, pagination, and expected response shape. Include cache behavior and whether the caller needs a particular content model or site configuration. Adobe's AEM persisted-query guide explains that these queries have configuration-specific endpoints and can be cached at Dispatcher and CDN layers. Those details are part of the application contract, not optional migration notes.
Test the destination before changing it
For every existing query, find the supported DA Live retrieval path or mark a gap. Run representative queries against a staging corpus with multiple locales, missing fields, and more items than one page. Compare the returned identifiers and field values with the current AEM response. If a channel requires a filter or query shape that cannot be reproduced, retain its current delivery path or design an explicit index or service and price that work into the migration.
Make cutover a consumer decision
The release gate should include the application owner, not only the content team. Agree on output parity, cache invalidation, error handling, and fallback for each consumer. A successful authoring demo does not test a mobile app's filtered listing or a campaign's time-sensitive content lookup.
Adovo’s view
Content is useful only when the right consumer can find it at the right moment. Migrate the query contract before celebrating the repository move. Otherwise the cost of a clean authoring screen is paid by every downstream channel.
