i18n key agent generated duplicate message ids across feature branches

Not specified by the original author.

i18n key agent generated duplicate message ids across feature branches

TL;DR

Fixes the key-generation agent creating the same message id for different strings on different branches. Namespace generated ids by feature or content-hash them. Use when merges collide on message ids. Not for hand-written key collisions.

The error

Merge conflict: both branches generated message id onboarding.title for different strings.

Fix it

Step 1: List the colliding ids

node -e "console.log('find ids defined twice with different source text')"

Expected: You see the collisions and their branches.

Step 2: Rename with feature namespaces

node -e "console.log('prefix generated ids with the feature name')"

Expected: Each id is unique to its feature.

Step 3: Re-extract both branches and merge

node -e "console.log('confirm no id collisions remain')"

Expected: The merge is clean.

When to use this

• Two branches generated the same message id
• The key agent uses short generic names

When NOT to use this

• A human typed the same key twice, rename it by hand
• The ids match and the strings match, that is a true duplicate to merge

Tool and version compatibility

• Any auto key-generation agent
• i18next, Lingui, and FormatJS key schemes

Variant phrasings

collisions within one branch

The generator ran twice with different counters. Make generation deterministic.

ids collide after a rebase

Rebasing replays generation. Regenerate ids after the rebase.

Why it happens

Simple key generators produce short readable ids from the string's position or a counter. Two branches working independently generate the same ids for different strings, and the merge cannot tell them apart.

Edge cases

• Content-hash ids never collide but are unreadable; namespace them for humans
• Renaming ids orphans existing translations; migrate the TMS too
• Deterministic generation from file path plus string is the most robust scheme

Provenance

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

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

Thread query: i18n key agent generated duplicate message ids across feature branches

TL;DR: Fixes the key-generation agent creating the same message id for different strings on different branches. Namespace generated ids by feature or content-hash them. Use when merges collide on message ids. Not for hand-written key collisions.

Not specified by the original author.

Fix react-intl defineMessages duplicate id collision

TL;DR

Two messages share the same id, so give every message a unique id or let the extractor generate them. Run the eslint rule that flags duplicates to find every collision at once. The usual cause is copy-pasting a defineMessages block and forgetting to change the id.

The error

Error: Duplicate message id: "app.header.title"
found in src/components/Header.js and src/components/Footer.js

Fix it

Step 1: Find every duplicate id in one pass

npx eslint src --rule '{"formatjs/no-duplicate-id": "error"}' | head -20

Expected: ESLint lists each duplicated id with both file locations.

Step 2: Rename the ids so each message is unique

grep -rn "app.header.title" src/ | head -10

Expected: You see both call sites and can rename one of them to match its component.

Step 3: Use namespaced ids by convention going forward

node -e "console.log('pattern: [page].[component].[purpose], e.g. footer.newsletter.title')"

Expected: New messages follow the pattern and collisions stop happening.

Step 4: Re-run lint to confirm zero duplicates

npx eslint src | tail -3

Expected: No duplicate-id errors remain.

When to use this

• The build or eslint reports a duplicate message id
• Two components accidentally share one id after copy-paste

When NOT to use this

• The ids are unique but the defaultMessage differs per locale, that is fine and expected
• You want shared ids on purpose, extract them to one shared module instead

Tool and version compatibility

• react-intl v5/v6/v7, eslint-plugin-formatjs
• babel-plugin-formatjs auto-id generation as alternative

Variant phrasings

ids generated by the extractor collide

Two identical defaultMessages in different files got the same hash id. Give one an explicit id to break the tie.

duplicate id across code-split bundles

The id is fine, the extractor just saw both bundles. Scope extraction per bundle or deduplicate at build time.

Why it happens

react-intl keys everything by message id, so two different defaultMessages with one id fight over the same slot in the catalog. Translators see one string, the app renders whichever won, and the other component shows the wrong copy.

Edge cases

• Auto-generated ids change when the defaultMessage changes, pin explicit ids for stable catalogs
• Shared messages should live in one module imported by both components, not duplicated
• The no-multiple-whitespaces rule often fires alongside, fix both while you are in there

Provenance

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

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

Thread query: react-intl definemessages duplicate id collision error

TL;DR: Two messages share the same id, so give every message a unique id or let the extractor generate them. Run the eslint rule that flags duplicates to find every collision at once. The usual cause is copy-pasting a defineMessages block and forgetting to change the id.

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.