{"section":"known-issues","requestedLocale":"en","requestedSlug":"updatethemeids-mutation-returns-504-but-content-migration-completes-successfully-in-background","locale":"en","slug":"updatethemeids-mutation-returns-504-but-content-migration-completes-successfully-in-background","path":"docs/en/known-issues/CMS/updatethemeids-mutation-returns-504-but-content-migration-completes-successfully-in-background.md","branch":"main","content":"## Summary\n\nWhen running the `updateThemeIds` mutation in `vtex.pages-graphql`, the request may return `504 Gateway Timeout` with an error such as `Request to vtex.pages-graphql@2.125.2 timed out after 11.0003652`. In some cases, especially for stores with a large amount of CMS content, this timeout affects only the HTTP response and not the migration itself. The content migration may continue in the background and finish successfully.\n\n## Simulation\n\n- Use a store with a large volume of CMS/Site Editor content.\n- Install the new major version of the same theme app in a production workspace.\n- In GraphQL IDE, select `vtex.pages-graphql@2.x`.\n- Run the `updateThemeIds` mutation, for example:\n\n- Observe that the response may return `504 Gateway Timeout` / `ProxyTimeout`, with a message stating that the request to `vtex.pages-graphql` timed out after about 11 seconds.\n- After the timeout, validate the workspace in Admin and storefront. In affected cases, the migrated content may start appearing correctly even though the mutation response returned an error.\n\n## Workaround\n\nAfter receiving the `504`, wait a few moments and verify that the migration has completed before retrying the mutation. Check `CMS > Pages`, Site Editor content, and storefront rendering in the target workspace. If the content was migrated successfully, no further action is required. Avoid triggering the same mutation multiple times in sequence, since the background process may already be running or completed."}