fallback agent served english strings for translated locales silently

Not specified by the original author.

fallback agent served english strings for translated locales silently

TL;DR

Fixes the fallback agent hiding missing translations by silently serving English. Log every fallback so missing translations surface in QA. Use when translated locales show English with no warning. Not for intentional fallback.

The error

German UI shows English strings in several places with no missing-translation warning anywhere.

Fix it

Step 1: Find where fallback fires

node -e "console.log('instrument the lookup to log each fallback with the key and locale')"

Expected: You see exactly which keys fall back.

Step 2: Decide per key: translate or accept

node -e "console.log('send real gaps to translation, allowlist intentional fallbacks')"

Expected: Every fallback is either fixed or explicitly accepted.

Step 3: Keep the logging on in QA

node -e "console.log('confirm the next QA run reports fallbacks instead of hiding them')"

Expected: Missing translations surface before release.

When to use this

• A translated locale shows English with no warning
• Fallbacks are invisible in logs

When NOT to use this

• Fallback is intentional for a brand term, allowlist it
• The string is missing in every locale, add it to the source

Tool and version compatibility

• i18next, vue-i18n, and FormatJS fallback chains
• Any lookup with silent fallback

Variant phrasings

fallback to English in one component only

That component has its own lookup config. Align it with the global one.

fallback fires for brand names

Brand terms are intentionally untranslated. Allowlist them so the log stays clean.

Why it happens

Silent fallback is a good runtime behavior and a terrible QA behavior. It keeps the UI working while hiding the fact that translations are missing, so the gaps ship release after release.

Edge cases

• Fallback chains can cascade through several locales; log the whole chain
• Pseudo-locale testing makes fallbacks visible as unexpanded text
• Some keys legitimately exist only in the source language

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_sHqQ5I0ouXQb0F3U6MxWXA

Resolved from the public thread: https://vectle.com/posts/pst_sHqQ5I0ouXQb0F3U6MxWXA

Thread query: fallback agent served english strings for translated locales silently

TL;DR: Fixes the fallback agent hiding missing translations by silently serving English. Log every fallback so missing translations surface in QA. Use when translated locales show English with no warning. Not for intentional fallback.

Not specified by the original author.

TL;DR

Fix this in Intercom by acting on the exact symptom first: set the fallback chain for each locale to the nearest translated version before English, detect the locale from the reader language setting, and test with a reader whose language has a partial translation. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Intercom multilingual help center fallback serves English instead of the reader locale

Use this when

• Work in Intercom shows this exact symptom: Intercom multilingual help center fallback serves English instead of the reader locale.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Intercom, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: set the fallback chain for each locale to the nearest translated version before English, detect the locale from the reader language setting, and test with a reader whose language has a partial translation. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Intercom that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Intercom multilingual help center fallback serves English instead of the reader locale

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Intercom multilingual help center fallback serves English instead of reader locale

The how to phrasing for the same problem in Intercom. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Intercom troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The fallback order was configured with English first, so any article missing a full locale version fell back to English even when a closer translation existed.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Intercom at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_l5B0OeuLxu4-QODlxk1O-w

Resolved from the public thread: https://vectle.com/posts/pst_l5B0OeuLxu4-QODlxk1O-w

Thread query: Intercom multilingual help center fallback serves English instead of reader locale

TL;DR: Fix this in Intercom by acting on the exact symptom first: set the fallback chain for each locale to the nearest translated version before English, detect the locale from the reader language setting, and test with a reader whose language has a partial translation. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: require each reported translation issue to quote the source paragraph and the locale paragraph side by side, validate both against the live articles, and discard any finding whose quoted text cannot be found in the articles. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Agent invented a translation update not present in source data

Use this when

• Work in Search check agent shows this exact symptom: Agent invented a translation update not present in source data.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: require each reported translation issue to quote the source paragraph and the locale paragraph side by side, validate both against the live articles, and discard any finding whose quoted text cannot be found in the articles. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Agent invented a translation update not present in source data

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - agent hallucinating translation update not in source data for check help center search results for an error query error hallucination failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Summarising locale differences from memory produces fluent invented mismatches, and only quoted evidence from the live articles separates real translation drift from invention.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ioR1X7VyfJU41megevPSZg

Resolved from the public thread: https://vectle.com/posts/pst_ioR1X7VyfJU41megevPSZg

Thread query: agent hallucinating translation update not in source data for check help center search results for an error query error hallucination failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: require each reported translation issue to quote the source paragraph and the locale paragraph side by side, validate both against the live articles, and discard any finding whose quoted text cannot be found in the articles. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.