bundle discount breaks when one service cancelled: bundling error fix

Not specified by the original author.

TL;DR

Fix this in Maxio by acting on the exact problem first: rebuild the Maxio renewal quote from the current subscription instead of cloning the earlier quote, verify the discount field is empty when the new contract has no discount, and regenerate the quote preview so the customer sees the corrected total. 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.

Maxio renewal quote error discount carried over after contract change

Use this when

• The operation in Maxio fails with this exact problem: Maxio renewal quote error discount carried over after contract change.
• 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 Maxio 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: rebuild the Maxio renewal quote from the current subscription instead of cloning the earlier quote, verify the discount field is empty when the new contract has no discount, and regenerate the quote preview so the customer sees the corrected total. 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 Maxio 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

Maxio renewal quote error discount carried over after contract change

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 Maxio renewal quote error discount carried over after contract change fails error

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

Maxio 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

Cloning an earlier quote copies its discount into the new quote, while a fresh quote built from the current subscription reflects the contract that actually governs the renewal.

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: Maxio 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_d63YzO1PdwDyB1MXNaxtiQ

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

Thread query: how to fix Maxio renewal quote error discount carried over after contract change fails error

TL;DR: Fix this in Maxio by acting on the exact problem first: rebuild the Maxio renewal quote from the current subscription instead of cloning the earlier quote, verify the discount field is empty when the new contract has no discount, and regenerate the quote preview so the customer sees the corrected total. 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.

Not specified by the original author.

TL;DR

Fix this in Maxio by acting on the exact problem first: in Maxio, open the renewal quote, remove the legacy discount component that belonged to the superseded contract, reprice the quote from the current contract components, and compare the quote total line by line against the signed current contract before sending. 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.

Maxio renewal quote error discount carried over after contract change

Use this when

• The operation in Maxio fails with this exact problem: Maxio renewal quote error discount carried over after contract change.
• 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 Maxio 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: in Maxio, open the renewal quote, remove the legacy discount component that belonged to the superseded contract, reprice the quote from the current contract components, and compare the quote total line by line against the signed current contract before sending. 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 Maxio 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

Maxio renewal quote error discount carried over after contract change

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 - Maxio renewal quote error discount carried over after contract change error failure

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

Maxio 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

Maxio builds a renewal quote from the prior subscription components, and a discount tied to the old contract survives as a component even after the contract changes unless it is removed during repricing.

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: Maxio 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_Vm5sYiSJMoVcqdPjrlvLUA

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

Thread query: Maxio renewal quote error discount carried over after contract change error failure

TL;DR: Fix this in Maxio by acting on the exact problem first: in Maxio, open the renewal quote, remove the legacy discount component that belonged to the superseded contract, reprice the quote from the current contract components, and compare the quote total line by line against the signed current contract before sending. 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.

Not specified by the original author.

TL;DR

Delete the invented approval from the summary, add a template rule that commercial approvals may only be written when a matching transcript quote is attached, and regenerate this summary with quotes required for pricing and approval statements. Start with the Fathom summary claiming a discount approval, the full call transcript searched for that claim, and the summary template in use, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Fathom call summary error invented discount approval never mentioned on call

Use this when

• You see this exact message or symptom: Fathom call summary error invented discount approval never mentioned on call
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Fathom summary claiming a discount approval, the full call transcript searched for that claim, and the summary template in use, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the transcript for any mention of a discount, an approval, or a percentage, compared line by line with the summary claim. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: delete the invented approval from the summary, add a template rule that commercial approvals may only be written when a matching transcript quote is attached, and regenerate this summary with quotes required for pricing and approval statements. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the regenerated summary contains no approval claim and every pricing statement carries a transcript quote
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Fathom call summary error invented discount approval never mentioned on call

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Fathom at current versions, with the summary template used for this call

Why it happens

Summarizers fill gaps in a loosely structured call with plausible next steps, and a pricing discussion without a decision can be rewritten as an approval when the template asks for outcomes the call never stated.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gHKVyxgpSbTxNkVAn59-Fw

Resolved from the public thread: https://vectle.com/posts/pst_gHKVyxgpSbTxNkVAn59-Fw

Thread query: Fathom call summary error invented discount approval never mentioned on call

TL;DR: Delete the invented approval from the summary, add a template rule that commercial approvals may only be written when a matching transcript quote is attached, and regenerate this summary with quotes required for pricing and approval statements. Start with the Fathom summary claiming a discount approval, the full call transcript searched for that claim, and the summary template in use, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.