multi-year quote error year two pricing escalator not applied failure

Not specified by the original author.

TL;DR

Fix this in the proposal generator by acting on the exact message first: apply the contracted annual escalator to every recurring line for year two and later, compounding on the previous year, stamp each year subtotal with its rate, and reconcile the multi-year total against a hand calculation for the first renewal year. 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.

Multi-year quote error year two pricing escalator not applied

Use this when

• The operation in the proposal generator fails with this exact message: Multi-year quote error year two pricing escalator not applied.
• 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: apply the contracted annual escalator to every recurring line for year two and later, compounding on the previous year, stamp each year subtotal with its rate, and reconcile the multi-year total against a hand calculation for the first renewal year. 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 escalator was set on the quote header but the year two lines were cloned from year one without applying it, so renewal pricing stayed flat.

Variant phrasings

Multi-year quote error year two pricing escalator not applied

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: multi-year quote error year two pricing escalator not applied 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_bwxxecoGQT8mH9OcnwTcuA

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

Thread query: multi-year quote error year two pricing escalator not applied failure

TL;DR: Fix this in the proposal generator by acting on the exact message first: apply the contracted annual escalator to every recurring line for year two and later, compounding on the previous year, stamp each year subtotal with its rate, and reconcile the multi-year total against a hand calculation for the first renewal year. 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: validate every input for the task, price a multi-year deal with escalators, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. 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 failed to complete price a multi-year deal with escalators error

Use this when

• The operation in the proposal generator fails with this exact message: Agent failed to complete price a multi-year deal with escalators error.
• 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: validate every input for the task, price a multi-year deal with escalators, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. 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

One stage inside price a multi-year deal with escalators failed partway and the agent had no checkpoints or input validation, so the whole task was reported failed with no way to resume or see which stage broke.

Variant phrasings

Agent failed to complete price a multi-year deal with escalators error

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 failed to complete price a multi-year deal with escalators error 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/pstdqBS99QckN4lj57y1ryzg

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

Thread query: agent failed to complete price a multi-year deal with escalators error failure

TL;DR: Fix this in the proposal generator by acting on the exact message first: validate every input for the task, price a multi-year deal with escalators, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. 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 renewal pricing by acting on the exact problem first: compare the year two invoice amount against the contract uplift clause, issue a corrected renewal quote at the uplifted price, and add an uplift field to the quote template so the percentage is applied automatically on future multi-year renewals. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account first, then rerun the full scope and reconcile the results.

renewal uplift clause not applied error price stayed flat second year

Use this when

• The operation in renewal pricing fails with this exact problem: renewal uplift clause not applied error price stayed flat second year.
• The same failure repeats on retry with unchanged inputs.
• A renewal, reminder, quote or playbook step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a commercial decision such as price or terms. That is a negotiation, not this failure.

Steps

1. Reproduce the failure on one named account in renewal pricing and record the full problem text plus the account, contract or quote involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: compare the year two invoice amount against the contract uplift clause, issue a corrected renewal quote at the uplifted price, and add an uplift field to the quote template so the percentage is applied automatically on future multi-year renewals. Verify: the single failing account now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring accounts, contracts or quotes that share the same automation, template or sync, because this class of failure rarely affects only one account. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in renewal pricing 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 against the source of truth, the signed contract, the billing record or the CRM opportunity, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the account so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

renewal uplift clause not applied error price stayed flat second year

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single account proof, then the full rerun.

How to fix - how to fix renewal uplift clause not applied error price stayed flat second year fails error

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

renewal pricing troubleshooting for this failure

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

Why it happens

Without an uplift field on the template, the clause lives only in the contract document and nothing in the quoting flow asks for it, which is why flat pricing recurs until the template carries it.

Edge cases

• The account was amended, reassigned or re priced after the failing run started. Refresh the account state and reapply the fix against the current values, not the values from the failed run.
• The single account proof passes but the full rerun still fails on other accounts. Treat each remaining failure as its own scope, because a shared automation can hide more than one cause.
• The source systems disagree on the correct value. The signed contract governs dates and prices, the billing system governs amounts charged, and the CRM governs ownership; record which source won and why.

Compatibility: renewal pricing at current versions, plus the CRM, billing or CS platform the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

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

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

Thread query: how to fix renewal uplift clause not applied error price stayed flat second year fails error

TL;DR: Fix this in renewal pricing by acting on the exact problem first: compare the year two invoice amount against the contract uplift clause, issue a corrected renewal quote at the uplifted price, and add an uplift field to the quote template so the percentage is applied automatically on future multi-year renewals. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account first, then rerun the full scope and reconcile the results.