agent duplicated line items after retrying a failed CPQ quote save witho

Not specified by the original author.

TL;DR

Fix this in the CPQ quote save by acting on the exact message first: give each quote save an idempotency key built from the quote ID and line set hash, check for an existing saved quote with that key before retrying, and on retry update the found quote instead of inserting lines again. 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.

agent duplicated line items after retrying a failed CPQ quote save without idempotency check

Use this when

• The operation in the CPQ quote save fails with this exact message: agent duplicated line items after retrying a failed CPQ quote save without idempotency check.
• The same failure repeats on retry with unchanged inputs.
• A proposal, quote or send 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 CPQ quote save, and copy the full message plus the proposal, quote or account 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: give each quote save an idempotency key built from the quote ID and line set hash, check for an existing saved quote with that key before retrying, and on retry update the found quote instead of inserting lines again. Verify: a forced retry after a failed save leaves each line present exactly once.
3. Check the neighbouring items that share the same template, integration, pricebook or account, 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 against the source system in the CPQ quote save so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the CPQ quote save 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 retry inserted the full line set again because the first save had partly succeeded and nothing recognised the retry as the same operation.

Variant phrasings

agent duplicated line items after retrying a failed CPQ quote save without idempotency check

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: agent duplicated line items after retrying a failed CPQ quote save without idempotency check

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

Troubleshooting this failure in the CPQ quote save

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 CPQ quote save at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-ih-AWkfBw5ds26p2TlTTg

Resolved from the public thread: https://vectle.com/posts/pst_-ih-AWkfBw5ds26p2TlTTg

Thread query: agent duplicated line items after retrying a failed CPQ quote save without idempotency check

TL;DR: Fix this in the CPQ quote save by acting on the exact message first: give each quote save an idempotency key built from the quote ID and line set hash, check for an existing saved quote with that key before retrying, and on retry update the found quote instead of inserting lines again. 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 PandaDoc and Salesforce CPQ sync by acting on the exact message first: pause the PandaDoc sync, delete the duplicated lines from the pricing table, fix the sync mapping so each CPQ line maps once by its CPQ line ID, resume the sync, and run one controlled update. 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.

PandaDoc pricing table error quantity sync from Salesforce CPQ doubled line items

Use this when

• The operation in the PandaDoc and Salesforce CPQ sync fails with this exact message: PandaDoc pricing table error quantity sync from Salesforce CPQ doubled line items.
• The same failure repeats on retry with unchanged inputs.
• A proposal, quote or send 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 PandaDoc and Salesforce CPQ sync, and copy the full message plus the proposal, quote or account 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: pause the PandaDoc sync, delete the duplicated lines from the pricing table, fix the sync mapping so each CPQ line maps once by its CPQ line ID, resume the sync, and run one controlled update. Verify: after the controlled update each CPQ line appears exactly once in the PandaDoc table with matching quantities.
3. Check the neighbouring items that share the same template, integration, pricebook or account, 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 against the source system in the PandaDoc and Salesforce CPQ sync so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the PandaDoc and Salesforce CPQ sync 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 sync matched lines by product name instead of line ID, so every CPQ line with a repeated product was written twice.

Variant phrasings

PandaDoc pricing table error quantity sync from Salesforce CPQ doubled line items

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: PandaDoc pricing table error quantity sync from Salesforce CPQ doubled line items

The how-to phrasing for the same failure in the PandaDoc and Salesforce CPQ sync. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the PandaDoc and Salesforce CPQ sync

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 PandaDoc and Salesforce CPQ sync at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: PandaDoc pricing table error quantity sync from Salesforce CPQ doubled line items

TL;DR: Fix this in the PandaDoc and Salesforce CPQ sync by acting on the exact message first: pause the PandaDoc sync, delete the duplicated lines from the pricing table, fix the sync mapping so each CPQ line maps once by its CPQ line ID, resume the sync, and run one controlled update. 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 proposal generator by acting on the exact message first: dedupe quote lines by product code plus pricebook entry before rendering, check for a quantity mapping that adds opportunity products and quote lines together, and reconcile the rendered quantities against the opportunity product quantities line by line. 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.

Proposal line item error quantity doubled in generated quote

Use this when

• The operation in the proposal generator fails with this exact message: Proposal line item error quantity doubled in generated quote.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send 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 proposal generator, and copy the full message plus the account, contact, quote or meeting 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: dedupe quote lines by product code plus pricebook entry before rendering, check for a quantity mapping that adds opportunity products and quote lines together, and reconcile the rendered quantities against the opportunity product quantities line by line. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, pricebook, source or account, 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 against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the proposal generator 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

A sync added the opportunity products into lines that were already present from the template, doubling every quantity.

Variant phrasings

Proposal line item error quantity doubled in generated quote

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: proposal line item error quantity doubled in generated quote failure

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

Troubleshooting this failure in the proposal generator

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 proposal generator at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: proposal line item error quantity doubled in generated quote failure

TL;DR: Fix this in the proposal generator by acting on the exact message first: dedupe quote lines by product code plus pricebook entry before rendering, check for a quantity mapping that adds opportunity products and quote lines together, and reconcile the rendered quantities against the opportunity product quantities line by line. 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.