API version: Admin GraphQL 2026-10, development store, Dawn-based main theme, unpublished locale es. All keys are SINGLE_LINE_TEXT_FIELD; keys don’t overlap between calls or runs.
Context. A theme’s locale content resource (gid://shopify/OnlineStoreThemeLocaleContent/<themeId>) has about 4,500 keys, and translationsRegister takes at most 100 keys per call (TOO_MANY_KEYS_FOR_RESOURCE above that), so a language has to be written in several calls.
Steps to reproduce:
translationsRegisterwith 100 keys of the locale content fores. No userErrors;translationsechoes all 100.- Right after it returns, the same call with 50 other keys of the same resource and locale. No userErrors; echoes all 50.
- Read back with
translatableResource(resourceId) { translations(locale: "es") { key value } }for a few minutes.
Expected: 150 translations served. Actual: only the 50 of the second call; the first call’s 100 keep their previous values.
mutation($id: ID!, $translations: [TranslationInput!]!) {
translationsRegister(resourceId: $id, translations: $translations) {
userErrors { field message code }
translations { key value }
}
}
Runs on 2026-10-20 (UTC, request start; X-Request-ID):
- Back to back, first call lost. 11:46:10, 100 keys,
2b657cb0-eb61-487e-bcfb-f7c430741bb3-1792496770→ then 11:46:12, 50 keys,cc685750-b35f-432f-9e18-668d3a9a5ede-1792496772. After ~30 s: 0/100 and 50/50 served. - Second call sent after the
locales/es.jsonchecksum changed (~1–1.5 s after the first response), first call still lost. 11:50:36, 50 keys,b600aa3f-5b55-4f01-83b3-6ecc3f124944-1792497036→ 11:50:39, 50 keys,48ac2b21-97d4-45ae-9690-d086dc18ae62-1792497039: 0/50 and 50/50. Again 11:50:56,8b5063e5-9a40-4d6e-b542-4ad2fc3772de-1792497056→ 11:50:59,0b18a7ee-cac5-4c68-abc8-34b89e6b7e83-1792497059: 0/50 and 50/50. - Waiting until the first call’s values are served, both kept. 11:46:46, 100 keys,
55916df4-a3ed-4c12-8b80-f7a2d940b0ff-1792496806; served ~3 s after the response. Then 11:46:52, 50 keys,cdda2d71-f795-4a76-a76c-be5cb85d7f0a-1792496812: 100/100 and 50/50. - bulkOperationRunMutation, one
translationsRegisterper JSONL line, same resource,es. Each operation COMPLETED with no userErrors on any line, and in each the first line was never served (checked ~45 s later):gid://shopify/BulkOperation/10834217632113(12:25:32–12:25:42, 3 × 50 keys): served 0, 50, 50gid://shopify/BulkOperation/10834222055793(12:26:35–12:26:45, 100 + 50): served 0, 50gid://shopify/BulkOperation/10834225070449(12:27:39–12:27:53, 6 × 50): served 0, 50, 50, 50, 50, 50
Other observations:
locales/es.json(checksum, size,updatedAt) changes as soon as the call returns, buttranslatableResourceserves the new values only ~2–4 s later.OnlineStoreTheme.processingstays false throughout.- JSON templates and section groups of the same theme are not affected: written in parallel with the locale content, or in two calls back to back, nothing is lost.
It looks as if the second write starts from the locale file version that was served before the first write was applied, and then replaces the file. The translationsRegister docs say a registered translation is visible immediately, and say nothing about ordering. A similar report with parallel calls: Online store theme race condition on translaltion updates
Questions: Is this expected? Is there a supported way to write more than 100 keys of a theme’s locale content, or a signal that a write has been applied, other than polling the translations back? We can share the store domain privately.