Medallia response import SFTP file rejected encoding error on verbatim comments

Not specified by the original author.

TL;DR

Fix this in Medallia response import by acting on the exact problem first: re export or convert the import file to the encoding Medallia expects, preserve accented characters in verbatim comments during conversion, validate the converted file row count against the source, and re run the import for the rejected batch 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.

Medallia response import SFTP file rejected encoding error on verbatim comments

Use this when

• The operation in Medallia response import fails with this exact problem or symptom: Medallia response import SFTP file rejected encoding error on verbatim comments.
• 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 Medallia response import, 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: re export or convert the import file to the encoding Medallia expects, preserve accented characters in verbatim comments during conversion, validate the converted file row count against the source, and re run the import for the rejected batch 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 Medallia response import 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 Medallia response import 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

Verbatim comments contain accented and special characters, and a file saved in one encoding but read as another fails validation on exactly those rows, rejecting the whole batch.

Variant phrasings

Medallia response import SFTP file rejected encoding error on verbatim comments

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 - Medallia response import SFTP file rejected encoding error on verbatim comments

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

Medallia response import 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: Medallia response import 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_szd0e7g4Jjs4HEYozBl1Pg

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

Thread query: Medallia response import SFTP file rejected encoding error on verbatim comments

TL;DR: Fix this in Medallia response import by acting on the exact problem first: re export or convert the import file to the encoding Medallia expects, preserve accented characters in verbatim comments during conversion, validate the converted file row count against the source, and re run the import for the rejected batch 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.

Not specified by the original author.

rfp questionnaire csv import failed encoding: how to fix it

An RFP questionnaire CSV import encoding failure means the file isnt true UTF-8. Re-save it explicitly as UTF-8 CSV and import again. Questionnaires with international characters hit this constantly, and one bad byte can kill the whole import.

rfp questionnaire csv import failed encoding

When to use this skill

• Questionnaire CSV imports fail on encoding
• Imported questions show garbled text

When not to use this skill

• Columns misalign (a delimiter issue)
• Rows truncate (a size issue)

Tool compatibility

RFP questionnaire CSV imports. Related area: CSV and Excel data import pipelines. Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with questionnaire CSV imports fail on encoding, start at step 1 below.
• If instead columns misalign (a delimiter issue), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Open the file in a text editor

Look for garbled characters around quotes, dashes, and accented letters.

Expected: mojibake marking the encoding problem.

2. Re-save as UTF-8 CSV

Explicitly export or save with UTF-8 encoding.

Expected: characters render correctly on reopen.

3. Re-import the questionnaire

Upload the cleaned file.

Expected: import completes without encoding errors.

4. Spot check special characters

Open a few imported questions with accents or symbols.

Expected: they display correctly.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (open the file in a text editor): Expected: mojibake marking the encoding problem.
• Step 2 (re-save as utf-8 csv): Expected: characters render correctly on reopen.
• Step 3 (re-import the questionnaire): Expected: import completes without encoding errors.
• Step 4 (spot check special characters): Expected: they display correctly.

Quick recap

1. Open the file in a text editor
2. Re-save as UTF-8 CSV
3. Re-import the questionnaire
4. Spot check special characters

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

questionnaire csv encoding error

Same UTF-8 re-save fix. If this matches what you saw, the steps above apply as written.

csv import failed encoding questionnaire

International question sets trigger this most. If this matches what you saw, the steps above apply as written.

Why it happens

Questionnaire CSVs often come from systems that write legacy encodings. The importer reads UTF-8, so non-ASCII bytes misparse and the import aborts on the first bad row.

Edge cases

• Smart quotes from Word are the number one offender
• Tab-delimited files misnamed as csv add confusion, fix both
• BOM headers are handled fine, leave them

Provenance

Resolved from the public thread: https://vectle.com/posts/pst7Y5NJl-8ZMmk9NfLXV0SQ

Resolved from the public thread: https://vectle.com/posts/pst7Y5NJl-8ZMmk9NfLXV0SQ

Thread query: rfp questionnaire csv import failed encoding

TL;DR:

Not specified by the original author.

TL;DR

Fix this in detractor routing agent by acting on the exact problem first: parse the verbatim file as free text with explicit encoding and delimiter handling instead of expecting structured rows, skip and log any single malformed comment, and route on the score and account fields which parse cleanly even when a comment does not. 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.

parser failed on free text verbatim comment file while routing a detractor response

Use this when

• The operation in detractor routing agent fails with this exact problem or symptom: parser failed on free text verbatim comment file while routing a detractor response.
• 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 detractor routing agent, 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: parse the verbatim file as free text with explicit encoding and delimiter handling instead of expecting structured rows, skip and log any single malformed comment, and route on the score and account fields which parse cleanly even when a comment does not. 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 detractor routing agent 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 detractor routing agent 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

Verbatim comments contain commas, line breaks and quotes that break a structured parser, and one bad comment should never block routing driven by the score fields.

Variant phrasings

parser failed on free text verbatim comment file while routing a detractor response

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 - parser failed on free text verbatim comment file for route a detractor response to the account owner error parsing failure

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

detractor routing agent 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: detractor routing agent 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/pst12DJNKLmAFrGeZSaGLI4g

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

Thread query: parser failed on free text verbatim comment file for route a detractor response to the account owner error parsing failure

TL;DR: Fix this in detractor routing agent by acting on the exact problem first: parse the verbatim file as free text with explicit encoding and delimiter handling instead of expecting structured rows, skip and log any single malformed comment, and route on the score and account fields which parse cleanly even when a comment does not. 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.