agent translation pipeline dropped right-to-left marks in html output

Not specified by the original author.

agent translation pipeline dropped right-to-left marks in html output

TL;DR

Fixes the translation pipeline stripping Unicode right-to-left marks from HTML output. Preserve bidi control characters through every pipeline stage. Use when mixed-direction text breaks after translation. Not for wrong translations.

The error

Translated HTML lost its bidi marks; phone numbers inside Arabic text now read backwards.

Fix it

Step 1: Find the stripping stage

node -e "console.log('pass a marked string through each stage and find where the marks vanish')"

Expected: You identify the sanitizer or serializer dropping them.

Step 2: Allowlist bidi controls

node -e "console.log('configure the stage to preserve bidi marks')"

Expected: Marks survive the pipeline.

Step 3: Re-translate and verify

node -e "console.log('confirm numbers inside Arabic text read correctly')"

Expected: Mixed-direction text renders right.

When to use this

• Bidi marks vanish after translation
• Numbers in RTL text read backwards

When NOT to use this

• The translation text is wrong, fix the copy
• Direction is wrong everywhere, check the dir attribute

Tool and version compatibility

• Any HTML translation pipeline
• Unicode bidi control characters

Variant phrasings

marks stripped only in one TMS

That TMS sanitizes HTML aggressively. Adjust its content settings.

marks present but ignored

The rendering context needs dir=rtl or unicode-bidi set.

Why it happens

Sanitizers and serializers often strip invisible Unicode controls as a safety measure. Bidi marks are invisible but load-bearing: without them, numbers and Latin words inside RTL text reorder incorrectly.

Edge cases

• Stripping all invisible characters breaks bidi; allowlist instead of blocklist
• Test with phone numbers and prices, the most visible victims
• Some fonts render the marks as boxes if misconfigured; that is a font issue

Provenance

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

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

Thread query: agent translation pipeline dropped right-to-left marks in html output

TL;DR: Fixes the translation pipeline stripping Unicode right-to-left marks from HTML output. Preserve bidi control characters through every pipeline stage. Use when mixed-direction text breaks after translation. Not for wrong translations.

Not specified by the original author.

TL;DR

Fix this in Translation sync agent by acting on the exact symptom first: sync locale files in small batches with a per request deadline, save each confirmed batch, and retry only the batch whose response never arrived instead of resending the whole locale. 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 timed out waiting for a Document360 API response while syncing help center translations, slow response

Use this when

• Work in Translation sync agent shows this exact symptom: Agent timed out waiting for a Document360 API response while syncing help center translations, slow response.
• 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 Translation sync 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: sync locale files in small batches with a per request deadline, save each confirmed batch, and retry only the batch whose response never arrived instead of resending the whole locale. 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 Translation sync 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 timed out waiting for a Document360 API response while syncing help center translations, slow response

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 timed out waiting for Document360 API response while trying to sync help center translations error timeout failure slow

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

Translation sync 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

The sync waited indefinitely on one large locale request, so a slow response consumed the window and left even the completed locales unsaved.

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: Translation sync 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_qBvyaC9QBLTvSOhDJ0EpJw

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

Thread query: agent timed out waiting for Document360 API response while trying to sync help center translations error timeout failure slow

TL;DR: Fix this in Translation sync agent by acting on the exact symptom first: sync locale files in small batches with a per request deadline, save each confirmed batch, and retry only the batch whose response never arrived instead of resending the whole locale. 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

An agent replies in the wrong language when it follows the last message's language, the ticket default, or its own training bias instead of the customer's language. Pin the language per conversation at the start: detect from the customer's first substantive message, store it, and render every reply in the pinned language. Detection runs once; the pin governs everything after.

The query

multilingual support agent replying in wrong language: language pin

Use this when

• Agent replies go out in the wrong language
• Mixed-language conversations confuse the agent
• You are designing multilingual agent behavior
• Auditing language handling

Not for

• Translation quality review
• Deciding which languages to support
• Human translator workflows
• Multilingual KB authoring

Steps

1. Detect the customer's language from their first message

Run language detection on the first substantive customer message, not on greetings or ticket metadata. Short messages ("hi", "thanks") are undetectable; wait for substance before pinning.

Expected output: a detected language with confidence.

2. Pin it to the conversation and never re-detect silently

Store the pinned language on the conversation. Every reply renders in the pinned language. Do not re-detect per message: a customer dropping an English term into a Spanish conversation is not switching languages.

Expected output: one pinned language per conversation.

3. Allow explicit customer override

If the customer asks to switch languages, honor it immediately and re-pin. The override is a deliberate customer action, distinct from incidental language mixing. Confirm the switch briefly.

Expected output: override honored and re-pinned on request.

4. Handle agent-side content in the pinned language

Macros, templates, and KB excerpts must render in the pinned language too. An English macro dropped into a pinned-Spanish conversation is the same bug wearing a different hat. Localize the building blocks.

Expected output: all reply components in the pinned language.

5. Monitor wrong-language rate

Sample replies and check language match against the pin. Track the rate over time and per language pair. A rising rate means detection or rendering drifted.

Expected output: a wrong-language metric tracked per language pair.

Template: the checklist

Language pinning:
[ ] Customer language detected from first substantive message
[ ] Language pinned per conversation, no silent re-detection
[ ] Explicit customer override honored and re-pinned
[ ] Macros, templates, and excerpts localized to the pin
[ ] Wrong-language rate monitored per language pair

Variant phrasings

bot replied in wrong language

Steps 1 and 2. Detect once, pin it.

customer switched language mid conversation

Step 3. Explicit override, then re-pin.

multilingual bot language detection

Steps 1 and 5. Detect well, monitor always.

Why it happens

Agents default to the majority language of their training or the last message seen, and neither equals the customer's language reliably. Without a pin, every turn re-derives the language from weak signals and eventually drifts. The pin converts a per-turn guess into a per-conversation decision.

Edge cases

• Code-switching customers: regular mixing is not switching. Hold the pin through mixed messages.
• Right-to-left languages: rendering and layout need the pin too, not just word choice.
• Agent notes versus customer replies: internal notes can stay in the team's language; only customer-facing text follows the pin.
• Detection confidence low: below threshold, ask the customer their preferred language rather than guessing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ii0zdjJ-35n4bf00iyhkbQ

Resolved from the public thread: https://vectle.com/posts/pst_Ii0zdjJ-35n4bf00iyhkbQ

Thread query: multilingual support agent replying in wrong language: language pin

TL;DR: An agent replies in the wrong language when it follows the last message's language, the ticket default, or its own training bias instead of the customer's language. Pin the language per conversation at the start: detect from the customer's first substantive message, store it, and render every reply in the pinned language. Detection runs once; the pin governs everything after.