| # Manual Testing: CMS Alt Text Updater DDA Migration | |
| ## What changed | |
| `RecommendationCmsItemAltTextUpdater` now reads via `CMSItemService.getItems` and writes via `CMSItemService.patchItems` instead of the legacy `getCMSItems`/`updateCMSItemPartial` path. | |
| ## Automated coverage | |
| - **Unit tests** (`cmsItemAltTextUpdater.test.ts`): cover all field types (ImageRef, MultiImage, RichText node array, RichText HTML), error handling, and patchItems error propagation | |
| - **Integration test** (`cmsItemAltTextUpdater_test.ts`): exercises a real ImageRef field update against both storage layers (Mongo and PG) |
Roope's RFC: Slack thread | Confluence design note | PR #112752
cms_component_usages is a PG table that indexes which components are used in which RTF field of which CMS item (CMSAUTH-5260). Collection schemas live in Mongo, usages in PG, so they can drift. The most common reads are cross-collection ("where is component X used?"), so read-time filtering via per-result PG-to-Mongo liveness checks is too expensive.
Status: Feature complete in beta. Promotion to v2 blocked on flag rollout to 100%.
CMS_COLLECTION_FIELD_GROUPS
In updateCMSItems.ts, skipUniqueValidation and skipItemRefValidation are coupled. Both read from opts.skipUniqueValidation:
// entrypoints/server/lib/logic/cms/items/updateCMSItems.ts, lines 408-413
skipUniqueValidation:
isSubsequentPublicationOperation ||
Date: 2026-06-24 Zendesk: #1152735 Triage thread: #triage-build-content First spotted: Aaron flagged during June 17 deploy
BadArgumentError: Invalid argument provided: Duplicate locales provided
109,574 errors across 12,062 unique sites in 3 days (June 8-10, 2026), all from sitemap generation during publish:
[sitemap] Failed to get published items for draft changes items
AppError [BadDatabaseStateError]: Expected a non-nullable string
at intoNonNull (CMSItem.ts:298)
getItemsInCollections in entrypoints/server/lib/sitemapUtils.ts builds a draftChangesPublishedItemsQuery to fetch published slugs for draft-changes items. That query is missing name in its returnFields. On PG-backed collections, the CMS storage layer's CMSItem.get name accessor calls intoNonNull, which throws BadDatabaseStateError: Expected a non-nullable string when name is undefined. The error is caught silently and logged as logger.warn, causing all draft-changes items for that collection to be dropped from the sitemap.
Fix: Add {field: {slug: 'name'}, include: true} to the live query's returnFields (PR #111007).
Sites with many published branch staging domains accumulate distinct live publications. During Single Item Publish (SIP), writeToAllLive fans out CMS writes to every distinct lastPublicationId across all domains, including branch domains. This scales linearly with the number of distinct publications.
Example: Synthesia (enterprise, localized, custom staging domain) has 8 live publications, including several from branch domains published in April/early May that were never merged or deleted. SIP traces show 43-46s durations, with users experiencing spinning publish buttons, 504 timeouts, and items stuck in "Changes in Draft."