glossary agent failed to sync term changes to in-progress jobs

Not specified by the original author.

glossary agent failed to sync term changes to in-progress jobs

TL;DR

Fixes the glossary agent leaving in-progress jobs on old terms after a glossary update. Propagate term changes to active jobs or re-apply the glossary. Use when jobs use outdated terms after a glossary edit. Not for jobs started after the change.

The error

Glossary term updated yesterday; three in-progress jobs still use the old term.

Fix it

Step 1: Find the stale jobs

node -e "console.log('list active jobs started before the glossary update')"

Expected: You have the affected job ids.

Step 2: Re-apply the glossary to them

node -e "console.log('push the updated terms into each active job')"

Expected: The jobs pick up the new terms.

Step 3: Automate the propagation

node -e "console.log('hook glossary updates to re-apply on active jobs')"

Expected: Future updates propagate automatically.

When to use this

• In-progress jobs use outdated glossary terms
• The glossary was updated mid-project

When NOT to use this

• New jobs use the old term, check the glossary publish step
• The term is wrong everywhere, fix the glossary entry

Tool and version compatibility

• Any TMS with glossary versioning
• Crowdin, Phrase, and Lokalise glossaries

Variant phrasings

jobs partially updated

The propagation ran mid-job. Re-run it to completion.

translators overrode the new term

Reviewer overrides win; the agent should not fight them.

Why it happens

Jobs snapshot the glossary at creation. A term change afterwards does not retroactively update running jobs, so they keep applying the old term until someone re-applies.

Edge cases

• Decide whether in-flight translator edits outrank the new term
• Version glossaries so jobs record which version they used
• Notify translators when terms change mid-job

Provenance

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

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

Thread query: glossary agent failed to sync term changes to in-progress jobs

TL;DR: Fixes the glossary agent leaving in-progress jobs on old terms after a glossary update. Propagate term changes to active jobs or re-apply the glossary. Use when jobs use outdated terms after a glossary edit. Not for jobs started after the change.

Not specified by the original author.

Fix the Crowdin sync failing when the agent uploads a glossary

TL;DR

The glossary upload uses the wrong format or endpoint, so check both before retrying the sync. Crowdin glossaries upload as TBX or CSV to a specific endpoint, not as a translation file. Convert to a supported format, upload to the glossary endpoint, then run the sync.

The error

Agent: glossary upload failed, Crowdin sync aborted
upload to the translations endpoint returned 400

Fix it

Step 1: Check the glossary format

head -5 glossary.csv

Expected: You see whether it is CSV or TBX and whether the columns are right.

Step 2: Upload to the glossary endpoint, not translations

node -e "console.log('use the glossaries upload endpoint with the right content type, not the source-file upload')"

Expected: The upload targets glossaries.

Step 3: Confirm the glossary exists in the project

curl -s -H "your auth header https://api.crowdin.com/api/v2/projects/$CROWDIN_PROJECT_ID/glossaries | head -c 300

Expected: The glossary is listed.

Step 4: Rerun the sync

node scripts/crowdin-sync.js | tail -3

Expected: The sync completes with the glossary in place.

When to use this

• Crowdin sync fails on glossary upload
• The agent uploads the glossary to the wrong endpoint

When NOT to use this

• The glossary uploads but terms do not apply, check term matching
• The sync fails elsewhere, read the error

Tool and version compatibility

• Crowdin API v2 glossaries endpoints
• TBX and CSV glossary formats

Variant phrasings

glossary too large to upload

Split by language pair or domain. Huge glossaries also slow down matching.

terms with special characters break the CSV

Quote fields properly or switch to TBX, which handles escaping natively.

Why it happens

Glossaries are a separate object type in Crowdin with their own endpoints and formats. Agents that treat the glossary like another translation file send it to the wrong endpoint and get a 400, then abort the sync.

Edge cases

• Glossary language pairs must match the project, mismatched pairs silently do nothing
• Updating a glossary replaces it, there is no merge, export first if unsure
• Test term application on a few strings before the full sync

Provenance

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

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

Thread query: when agent tried to upload glossary the crowdin sync failed

TL;DR: The glossary upload uses the wrong format or endpoint, so check both before retrying the sync. Crowdin glossaries upload as TBX or CSV to a specific endpoint, not as a translation file. Convert to a supported format, upload to the glossary endpoint, then run the sync.

Not specified by the original author.

TL;DR

Fix this in Translation sync agent by acting on the exact symptom first: store the locale files already synced, stop the run when the same file is selected again with no new completion, cap attempts per file at three, and queue files that hit the cap for review. 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 stuck in a loop repeating the same locale file while syncing help center translations

Use this when

• Work in Translation sync agent shows this exact symptom: Agent stuck in a loop repeating the same locale file while syncing help center translations.
• 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: store the locale files already synced, stop the run when the same file is selected again with no new completion, cap attempts per file at three, and queue files that hit the cap for review. 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 stuck in a loop repeating the same locale file while syncing help center translations

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 stuck in loop repeating the same locale file while trying to sync help center translations error failure

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 marked a file complete only after the whole batch finished, so the first unfinished file was reselected on every pass and the run never advanced past it.

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_jqRO-yF-KuPppNUcS8Ws2w

Resolved from the public thread: https://vectle.com/posts/pst_jqRO-yF-KuPppNUcS8Ws2w

Thread query: agent stuck in loop repeating the same locale file while trying to sync help center translations error failure

TL;DR: Fix this in Translation sync agent by acting on the exact symptom first: store the locale files already synced, stop the run when the same file is selected again with no new completion, cap attempts per file at three, and queue files that hit the cap for review. 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.