NPS data export error verbatim comments truncated at 255 characters err

Not specified by the original author.

TL;DR

Fix this in NPS export by acting on the exact problem first: find the longest verbatim in the source, follow it through the export file into the destination, fix the field type at the step where its length drops to 255, and re export the affected responses. 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 export error - verbatim comments truncated at 255 characters - fix

Use this when

• The operation in NPS export fails with this exact problem or symptom: NPS export error - verbatim comments truncated at 255 characters - fix.
• 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 export, 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: find the longest verbatim in the source, follow it through the export file into the destination, fix the field type at the step where its length drops to 255, and re export the affected responses. 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 export 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 export 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

Truncation at exactly 255 characters is a field type limit, not a content problem, and tracing one long comment pinpoints which step enforces that limit.

Variant phrasings

NPS export error - verbatim comments truncated at 255 characters - fix

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 - how to fix NPS data export error verbatim comments truncated at 255 characters fails error

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

NPS export 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 export 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_TrLRpz8sSS9lYaqvuSh4IA

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

Thread query: how to fix NPS data export error verbatim comments truncated at 255 characters fails error

TL;DR: Fix this in NPS export by acting on the exact problem first: find the longest verbatim in the source, follow it through the export file into the destination, fix the field type at the step where its length drops to 255, and re export the affected responses. 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.

TL;DR

Fix this in NPS export by acting on the exact problem first: change the export destination field and the export mapping from a short text type capped at 255 characters to a long text type, rerun the export, and spot check the longest comments against the source to confirm full text survives. 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 export error - verbatim comments truncated at 255 characters

Use this when

• The operation in NPS export fails with this exact problem or symptom: NPS export error - verbatim comments truncated at 255 characters.
• 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 export, 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: change the export destination field and the export mapping from a short text type capped at 255 characters to a long text type, rerun the export, and spot check the longest comments against the source to confirm full text survives. 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 export 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 export 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 comments land in a field typed for short text, so the export or the load silently cuts every comment at 255 characters even though the source holds the full text.

Variant phrasings

NPS export error - verbatim comments truncated at 255 characters

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 data export error verbatim comments truncated at 255 characters error failure

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

NPS export 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 export 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_7zRdaKHiVvLuPd-C-5Obew

Resolved from the public thread: https://vectle.com/posts/pst_7zRdaKHiVvLuPd-C-5Obew

Thread query: NPS data export error verbatim comments truncated at 255 characters error failure

TL;DR: Fix this in NPS export by acting on the exact problem first: change the export destination field and the export mapping from a short text type capped at 255 characters to a long text type, rerun the export, and spot check the longest comments against the source to confirm full text survives. 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.

TL;DR

Fix this in NPS verbatim redaction by acting on the exact problem first: extend the redaction patterns to cover phone numbers written with spaces, dashes, brackets and country codes as well as plain digit runs, re run redaction over stored verbatims, and sample the results by hand to confirm no readable number survives. 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 redaction misses phone numbers left in free text comments

Use this when

• The operation in NPS verbatim redaction fails with this exact problem or symptom: NPS verbatim redaction misses phone numbers left in free text 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 NPS verbatim redaction, 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: extend the redaction patterns to cover phone numbers written with spaces, dashes, brackets and country codes as well as plain digit runs, re run redaction over stored verbatims, and sample the results by hand to confirm no readable number survives. 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 verbatim redaction 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 verbatim redaction 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 redactor matched only one tightly formatted number pattern, and customers write numbers in many everyday formats, so the variants passed through untouched into shared reports.

Variant phrasings

NPS verbatim redaction misses phone numbers left in free text 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 - NPS verbatim redaction misses phone numbers left in free text comments

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

NPS verbatim redaction 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 verbatim redaction 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_v-Crk9HW97QcUmPYB9-EVQ

Resolved from the public thread: https://vectle.com/posts/pst_v-Crk9HW97QcUmPYB9-EVQ

Thread query: NPS verbatim redaction misses phone numbers left in free text comments

TL;DR: Fix this in NPS verbatim redaction by acting on the exact problem first: extend the redaction patterns to cover phone numbers written with spaces, dashes, brackets and country codes as well as plain digit runs, re run redaction over stored verbatims, and sample the results by hand to confirm no readable number survives. 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.