how to fix questionnaire intake error duplicate questions from customer vari

Not specified by the original author.

TL;DR

Fix this in the questionnaire intake parser by acting on the exact message first: teach the intake parser to follow the customer section names as data rather than expecting fixed headings, map the renamed sections to your standard sections in the intake map, and reparse the questionnaire. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

questionnaire intake error customer renamed sections parser dropped questions

Use this when

• The operation in the questionnaire intake parser fails with this exact message: questionnaire intake error customer renamed sections parser dropped questions.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in the questionnaire intake parser, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: teach the intake parser to follow the customer section names as data rather than expecting fixed headings, map the renamed sections to your standard sections in the intake map, and reparse the questionnaire. Verify: the reparse lists every question under its mapped section with zero dropped questions.
3. Check the neighbouring items that share the same config, template, feed 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. Compare the result counts, decisions or alerts against the source in the questionnaire intake parser so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the questionnaire intake parser on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
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 error, the fix applied and the evidence of success.

Why it happens

the parser dropped any section whose heading did not match its fixed list, so a customer rename silently removed whole sections.

Variant phrasings

questionnaire intake error customer renamed sections parser dropped questions

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

How to fix: how to fix questionnaire intake error customer renamed sections parser dropped questions fails

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

the questionnaire intake parser troubleshooting for this failure

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

Compatibility: the questionnaire intake parser at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_BM51mE-ic-vSEGPDPazqyQ

Resolved from the public thread: https://vectle.com/posts/pst_BM51mE-ic-vSEGPDPazqyQ

Thread query: how to fix questionnaire intake error customer renamed sections parser dropped questions fails

TL;DR: Fix this in the questionnaire intake parser by acting on the exact message first: teach the intake parser to follow the customer section names as data rather than expecting fixed headings, map the renamed sections to your standard sections in the intake map, and reparse the questionnaire. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in questionnaire intake by acting on the exact message first: normalize each incoming question by lowercasing, stripping punctuation and collapsing whitespace, group questions that normalize to near-identical text, map each group to one canonical library question, and keep a single answer per group. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

questionnaire intake error duplicate questions from customer variants

Use this when

• The operation in questionnaire intake fails with this exact message: questionnaire intake error duplicate questions from customer variants.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in questionnaire intake, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: normalize each incoming question by lowercasing, stripping punctuation and collapsing whitespace, group questions that normalize to near-identical text, map each group to one canonical library question, and keep a single answer per group. Verify: the deduped intake list shows one entry per canonical question and the total drops by the number of merged variants.
3. Check the neighbouring items that share the same config, template, feed 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. Compare the result counts, decisions or alerts against the source in questionnaire intake so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in questionnaire intake on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
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 error, the fix applied and the evidence of success.

Why it happens

customers reword the same question per template, so exact-text matching treats every variant as a new question and the queue fills with duplicates.

Variant phrasings

questionnaire intake error duplicate questions from customer variants

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

How to fix: how to fix questionnaire intake error duplicate questions from customer variants fails

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

questionnaire intake troubleshooting for this failure

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

Compatibility: questionnaire intake at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: how to fix questionnaire intake error duplicate questions from customer variants fails

TL;DR: Fix this in questionnaire intake by acting on the exact message first: normalize each incoming question by lowercasing, stripping punctuation and collapsing whitespace, group questions that normalize to near-identical text, map each group to one canonical library question, and keep a single answer per group. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the Loopio answer library by acting on the exact message first: in Loopio compare the duplicate retention answers against the current retention policy, keep the matching entry as canonical, archive the other, and refresh autofill so only the canonical entry can fill. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Loopio library error duplicate answers with different retention periods both active

Use this when

• The operation in the Loopio answer library fails with this exact message: Loopio library error duplicate answers with different retention periods both active.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in the Loopio answer library, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: in Loopio compare the duplicate retention answers against the current retention policy, keep the matching entry as canonical, archive the other, and refresh autofill so only the canonical entry can fill. Verify: library search for the retention question returns one active answer matching the policy periods.
3. Check the neighbouring items that share the same config, template, feed 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. Compare the result counts, decisions or alerts against the source in the Loopio answer library so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the Loopio answer library on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
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 error, the fix applied and the evidence of success.

Why it happens

the same question was answered twice in different years and both entries stayed active, so autofill picked between conflicting retention periods at random.

Variant phrasings

Loopio library error duplicate answers with different retention periods both active

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

How to fix: Loopio library error duplicate answers with different retention periods both active

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

the Loopio answer library troubleshooting for this failure

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

Compatibility: the Loopio answer library at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: Loopio library error duplicate answers with different retention periods both active

TL;DR: Fix this in the Loopio answer library by acting on the exact message first: in Loopio compare the duplicate retention answers against the current retention policy, keep the matching entry as canonical, archive the other, and refresh autofill so only the canonical entry can fill. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.