proposal generation failed error pricing table totals wrong failure

Not specified by the original author.

TL;DR

Fix this in the proposal generator by acting on the exact message first: recompute every line as quantity times unit price, apply the line discount, then add tax per line, compare each recomputed line and the grand total against the proposal table, and regenerate the table from the recomputed values rather than editing the printed numbers. 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 generation failed error pricing table totals wrong

Use this when

• The operation in the proposal generator fails with this exact message: Proposal generation failed error pricing table totals wrong.
• 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: recompute every line as quantity times unit price, apply the line discount, then add tax per line, compare each recomputed line and the grand total against the proposal table, and regenerate the table from the recomputed values rather than editing the printed numbers. 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

The table was rendered from a stale pricing snapshot taken before a line edit, so the printed totals described an earlier version of the quote.

Variant phrasings

Proposal generation failed error pricing table totals wrong

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 generation failed error pricing table totals wrong 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_viLyBDq2VvMRjAsHhekNjA

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

Thread query: proposal generation failed error pricing table totals wrong failure

TL;DR: Fix this in the proposal generator by acting on the exact message first: recompute every line as quantity times unit price, apply the line discount, then add tax per line, compare each recomputed line and the grand total against the proposal table, and regenerate the table from the recomputed values rather than editing the printed numbers. 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 agent run by acting on the exact message first: fingerprint each generated pricing table by a hash of its inputs, stop regeneration when the hash repeats after a template edit that does not affect pricing inputs, and surface the unchanged inputs to a human instead of looping. 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 agent loop regenerating the same pricing table after each template edit

Use this when

• The operation in the proposal agent run fails with this exact message: proposal agent loop regenerating the same pricing table after each template edit.
• 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 proposal agent run, 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: fingerprint each generated pricing table by a hash of its inputs, stop regeneration when the hash repeats after a template edit that does not affect pricing inputs, and surface the unchanged inputs to a human instead of looping. Verify: the run stops after one repeated hash and reports which inputs did not change.
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 proposal agent run 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 agent run 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 agent treated each regenerated table as new work because nothing compared outputs, so identical inputs produced an endless regeneration cycle.

Variant phrasings

proposal agent loop regenerating the same pricing table after each template edit

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 agent loop regenerating the same pricing table after each template edit

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

Troubleshooting this failure in the proposal agent run

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 agent run 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/pst8NRwWya3a6S2RoRmywAJw

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

Thread query: proposal agent loop regenerating the same pricing table after each template edit

TL;DR: Fix this in the proposal agent run by acting on the exact message first: fingerprint each generated pricing table by a hash of its inputs, stop regeneration when the hash repeats after a template edit that does not affect pricing inputs, and surface the unchanged inputs to a human instead of looping. 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 pricing table by acting on the exact message first: find the volume tier rule in the pricing table, remove the duplicate application by keeping the tier discount on the line rule only and clearing it from the table level rule, then recalculate the quote. 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 error volume discount tier applied twice in pricing table

Use this when

• The operation in the pricing table fails with this exact message: proposal error volume discount tier applied twice in pricing table.
• 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 pricing table, 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: find the volume tier rule in the pricing table, remove the duplicate application by keeping the tier discount on the line rule only and clearing it from the table level rule, then recalculate the quote. Verify: each line shows the tier discount applied once and the table total matches a hand check at the tier rate.
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 pricing table 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 pricing table 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 tier discount was configured at both line level and table level, so the engine multiplied it in twice.

Variant phrasings

proposal error volume discount tier applied twice in pricing table

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 proposal error volume discount tier applied twice in pricing table fails

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

Troubleshooting this failure in the pricing table

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 pricing table 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_SA0uhMZh6L65fPNM6l8GIA

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

Thread query: how to fix proposal error volume discount tier applied twice in pricing table fails

TL;DR: Fix this in the pricing table by acting on the exact message first: find the volume tier rule in the pricing table, remove the duplicate application by keeping the tier discount on the line rule only and clearing it from the table level rule, then recalculate the quote. 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.