Peakon comment translation error non English comments shown untranslated

Not specified by the original author.

TL;DR

Fix this in Peakon by acting on the exact problem first: in Peakon, open the comment language settings for the survey, confirm translation is enabled for the languages present in the comments, check the translation job ran for the current round and completed, rerun the translation for the comments that show untranslated, and compare one translated comment against its original before sharing the report. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

Peakon comment translation error non English comments shown untranslated

Use this when

• The operation in Peakon fails with this exact problem: Peakon comment translation error non English comments shown untranslated.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in Peakon and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Peakon, open the comment language settings for the survey, confirm translation is enabled for the languages present in the comments, check the translation job ran for the current round and completed, rerun the translation for the comments that show untranslated, and compare one translated comment against its original before sharing the report. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Peakon on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Peakon comment translation error non English comments shown untranslated

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - Peakon comment translation error non English comments shown untranslated

The how to phrasing for the same failure in Peakon. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Peakon troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Translation is a separate processing step per survey round, so comments collected in a new language appear untranslated until that step runs for the round.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: Peakon at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: Peakon comment translation error non English comments shown untranslated

TL;DR: Fix this in Peakon by acting on the exact problem first: in Peakon, open the comment language settings for the survey, confirm translation is enabled for the languages present in the comments, check the translation job ran for the current round and completed, rerun the translation for the comments that show untranslated, and compare one translated comment against its original before sharing the report. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and r

Not specified by the original author.

TL;DR

Fix this in Peakon by acting on the exact problem first: check one untranslated Peakon comment against the list of supported translation languages, confirm the comment is not a mixed language answer or a very short phrase the engine skips, exclude the unsupported languages from the report scope, and note which languages are untranslated so readers do not read them as negative English. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

how to fix Peakon comment translation error non English comments shown untranslated fails error

Use this when

• The operation in Peakon fails with this exact problem: how to fix Peakon comment translation error non English comments shown untranslated fails error.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in Peakon and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: check one untranslated Peakon comment against the list of supported translation languages, confirm the comment is not a mixed language answer or a very short phrase the engine skips, exclude the unsupported languages from the report scope, and note which languages are untranslated so readers do not read them as negative English. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Peakon on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

how to fix Peakon comment translation error non English comments shown untranslated fails error

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - how to fix Peakon comment translation error non English comments shown untranslated fails error

The how to phrasing for the same failure in Peakon. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Peakon troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

The translation engine skips comments it cannot classify or in languages it does not support, leaving them in the original text while the rest of the report reads translated.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: Peakon at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst7ZPUFNSgGqULRZsG-JnjA

Resolved from the public thread: https://vectle.com/posts/pst7ZPUFNSgGqULRZsG-JnjA

Thread query: how to fix Peakon comment translation error non English comments shown untranslated fails error

TL;DR: Fix this in Peakon by acting on the exact problem first: check one untranslated Peakon comment against the list of supported translation languages, confirm the comment is not a mixed language answer or a very short phrase the engine skips, exclude the unsupported languages from the report scope, and note which languages are untranslated so readers do not read them as negative English. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the resul

Not specified by the original author.

TL;DR

Fix this in NPS dashboard translation by acting on the exact problem first: enable translation for the verbatim field in the dashboard config, confirm the language detection step runs on the comment before display, and reprocess stored comments so Spanish verbatims gain a translated version instead of showing blank or original only. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

NPS verbatim comment in Spanish not translated in dashboard

Use this when

• The operation in NPS dashboard translation fails with this exact problem or symptom: NPS verbatim comment in Spanish not translated in dashboard.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in NPS dashboard translation, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: enable translation for the verbatim field in the dashboard config, confirm the language detection step runs on the comment before display, and reprocess stored comments so Spanish verbatims gain a translated version instead of showing blank or original only. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in NPS dashboard translation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in NPS dashboard translation so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

The dashboard translates only fields flagged for translation, and the verbatim field was added without that flag, so non English comments render untranslated while scores display normally.

Variant phrasings

NPS verbatim comment in Spanish not translated in dashboard

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - NPS verbatim comment in Spanish not translated in dashboard error error failure

The how-to phrasing for the same failure in NPS dashboard translation. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

NPS dashboard translation troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: NPS dashboard translation at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

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

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

Thread query: NPS verbatim comment in Spanish not translated in dashboard error error failure

TL;DR: Fix this in NPS dashboard translation by acting on the exact problem first: enable translation for the verbatim field in the dashboard config, confirm the language detection step runs on the comment before display, and reprocess stored comments so Spanish verbatims gain a translated version instead of showing blank or original only. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.