proposal generation error usage based pricing estimate uses wrong meter baseline

Not specified by the original author.

TL;DR

Fix this in the usage based pricing estimate by acting on the exact message first: replace the meter baseline in the estimate with the customer trailing 90 day actual usage for the same meter, rerun the estimate, and record the baseline period on the proposal. 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 error usage based pricing estimate uses wrong meter baseline

Use this when

• The operation in the usage based pricing estimate fails with this exact message: proposal generation error usage based pricing estimate uses wrong meter baseline.
• 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 usage based pricing estimate, 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: replace the meter baseline in the estimate with the customer trailing 90 day actual usage for the same meter, rerun the estimate, and record the baseline period on the proposal. Verify: the estimate uses the trailing 90 day baseline and the projected total moves in line with that usage.
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 usage based pricing estimate 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 usage based pricing estimate 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 estimate seeded its baseline from a default demo meter value instead of the customer actual meter history.

Variant phrasings

proposal generation error usage based pricing estimate uses wrong meter baseline

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 error usage based pricing estimate uses wrong meter baseline

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

Troubleshooting this failure in the usage based pricing estimate

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 usage based pricing estimate 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_WvMqKm-9MlMNaZdQ7cU0ng

Resolved from the public thread: https://vectle.com/posts/pst_WvMqKm-9MlMNaZdQ7cU0ng

Thread query: proposal generation error usage based pricing estimate uses wrong meter baseline

TL;DR: Fix this in the usage based pricing estimate by acting on the exact message first: replace the meter baseline in the estimate with the customer trailing 90 day actual usage for the same meter, rerun the estimate, and record the baseline period on the proposal. 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: 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

Use it for every new integration, including adding usage-based pricing to existing flat-rate subscriptions, prepaid credits, dimensional pricing, and high-volume event ingestion. - Basic usage-based billing (Billing Meters API): the lower-level primitive. A bug in your reporting code cannot be patched retroactively for the events already sent; you fix it going forward and credit the customer. Check the current docs before writing a line.

When to use

You are seeing this: Stripe now offers two usage-based billing paths, and your training data predates the split. Use this skill when you run into "Stripe usage-based billing: Metronome is primary, Billing Meters is legacy".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Stripe usage-based billing: pick Metronome for anything new

Stripe now offers two usage-based billing paths, and your training data predates the split. Picking the wrong one means building on the legacy primitive.

Which one

• Metronome: Stripe's primary usage-based billing platform. Use it for every new integration, including adding usage-based pricing to existing flat-rate subscriptions, prepaid credits, dimensional pricing, and high-volume event ingestion.
• Basic usage-based billing (Billing Meters API): the lower-level primitive. Stay on it only if you are already billing customers through Billing Meters today, or you need full compatibility with Connect, Checkout, Adaptive Pricing, or Workflows, where Metronome support is still limited.

How usage reporting works

1. Define what you meter: a Billing Meter maps incoming meter events to billable usage.
2. Report usage as it happens by sending meter events during the billing period. Do not batch everything at period end; late or missing events mean unbilled usage.
3. At period end, Stripe aggregates the events and invoices the total. Billing Meters reconciles usage at invoice time only, so there is no real-time usage visibility on the basic path. Metronome gives real-time visibility.
4. Usage reported during a trial is still recorded and billed when the trial converts (see the metered-with-trial skill for the ordering).

Validation rules that bite agents

• Billing meter event values with more than 15 digits are rejected as of the Dahlia API version. If your quantities come from 64-bit counters or nanosecond timestamps, scale them before reporting.
• Meter events are immutable once accepted. A bug in your reporting code cannot be patched retroactively for the events already sent; you fix it going forward and credit the customer.

The trap

Old guides and your parametric memory say "create a metered price with usage_type metered." That is the legacy shape. For anything new, the answer is Metronome, and the integration surface is different. Check the current docs before writing a line.

Stripe's usage-based billing doc states Metronome is the primary platform recommended for all new integrations and basic usage-based billing on Billing Meters remains for existing integrations, with the compatibility exceptions listed. The Dahlia changelog adds 15-digit validation for billing meter event values as a breaking change. Verified against live docs 2026-09-26.