{"section":"known-issues","requestedLocale":"en","requestedSlug":"search-resolver-applying-messages-translations-over-already-translated-content","locale":"en","slug":"search-resolver-applying-messages-translations-over-already-translated-content","path":"docs/en/known-issues/Intelligent Search/search-resolver-applying-messages-translations-over-already-translated-content.md","branch":"main","content":"## Summary\n\n\nThe Search Resolver (GraphQL layer for Intelligent Search) requests translations from the Messages service even for single-language stores or already translated content in a multi-language store.\n\nIn practice, these translations are made on top of the same \"from\" and \"to\" languages, but if the store has the automatic translation feature enabled, the string may change to something unexpected.\n\nThis affects especially strings with multiple words that may be considered from different languages, such as English words in the name of a product name that is majorly in French, and potentially dates (between the \"dd/mm/yyyy\" and \"mm/dd/yyyy\" notations).\n\n\n##\n\n## Simulation\n\n\n\n- Translate any content from the store's catalog to a language different from the default;\n- Make sure there is still at least one word in a different language than the translated one;\n- Check the storefront; it won't match the translation.\n\n\n##\n\n## Workaround\n\n\n\n- Disable the automatic translation;\n- Create translations for these contents using the same language as \"from\" and \"to\", for example, translating it from \"fr-FR\" to \"fr-FR\"."}