parent account mapping error expansion revenue double counted failure

Not specified by the original author.

TL;DR

Fix this in the parent account rollup by acting on the exact message first: deduplicate expansion revenue by child opportunity and child account id before rolling to the parent, so a child counted in two hierarchies is only counted once. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

parent account mapping error expansion revenue double counted failure

Use this when

• The operation in the parent account rollup fails with this exact message: parent account mapping error expansion revenue double counted failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 parent account rollup, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: deduplicate expansion revenue by child opportunity and child account id before rolling to the parent, so a child counted in two hierarchies is only counted once. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in the parent account rollup so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the parent account rollup 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 record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

An account present in both a geographic and a product hierarchy was summed twice at the parent.

Variant phrasings

parent account mapping error expansion revenue double counted failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in the parent account rollup

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

Troubleshooting this failure in the parent account rollup

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 parent account rollup 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_ksHQ7k3F-dCVMvPNqgTZRQ

Resolved from the public thread: https://vectle.com/posts/pst_ksHQ7k3F-dCVMvPNqgTZRQ

Thread query: parent account mapping error expansion revenue double counted failure

TL;DR: Fix this in the parent account rollup by acting on the exact message first: deduplicate expansion revenue by child opportunity and child account id before rolling to the parent, so a child counted in two hierarchies is only counted once. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the account hierarchy rollup by acting on the exact message first: add the subsidiary organisation ids and domains to the parent hierarchy mapping, then re-run the rollup from the child accounts up so subsidiary usage lands on the parent. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

account expansion error subsidiary usage not rolled up to parent failure

Use this when

• The operation in the account hierarchy rollup fails with this exact message: account expansion error subsidiary usage not rolled up to parent failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 account hierarchy rollup, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: add the subsidiary organisation ids and domains to the parent hierarchy mapping, then re-run the rollup from the child accounts up so subsidiary usage lands on the parent. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in the account hierarchy rollup so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the account hierarchy rollup 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 record 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 subsidiary existed as a standalone account with no parent link, so its usage rolled up to itself and the parent looked flat.

Variant phrasings

account expansion error subsidiary usage not rolled up to parent failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in the account hierarchy rollup

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

Troubleshooting this failure in the account hierarchy rollup

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 account hierarchy rollup 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/pstWjTv93atp6VPIizVvuEyw

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

Thread query: account expansion error subsidiary usage not rolled up to parent failure

TL;DR: Fix this in the account hierarchy rollup by acting on the exact message first: add the subsidiary organisation ids and domains to the parent hierarchy mapping, then re-run the rollup from the child accounts up so subsidiary usage lands on the parent. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Clari by acting on the exact message first: fix the Clari category mapping so each expansion opportunity sits in exactly one of new or upsell, correct the opportunity type values feeding both categories, refresh the forecast, and check the expansion commit total equals the sum of the underlying opportunities counted once. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.

Clari forecast error expansion commit double counted in both new and upsell categories

Use this when

• The operation in Clari fails with this exact message or symptom: Clari forecast error expansion commit double counted in both new and upsell categories.
• The same failure repeats on retry with unchanged inputs.
• Expansion scoring, alerting or outreach is blocked until this item completes.

Not for this skill when

• The message is an 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 quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Clari, and copy the full message plus the account, signal or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: fix the Clari category mapping so each expansion opportunity sits in exactly one of new or upsell, correct the opportunity type values feeding both categories, refresh the forecast, and check the expansion commit total equals the sum of the underlying opportunities counted once. Verify: the smallest failing scope now completes, or the named account, signal or job behaves as the fix predicts.
3. Check the neighbouring accounts, signals or jobs that share the same config, schema or source, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Clari 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.
5. Compare the result counts, scores or status against the source in Clari so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
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

When an opportunity type maps into two forecast categories, Clari sums it in both, and the commit total exceeds the real pipeline by that opportunity value.

Variant phrasings

Clari forecast error expansion commit double counted in both new and upsell categories

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - Clari forecast error expansion commit double counted in both new and upsell categories

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

Clari troubleshooting for this failure

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.

Edge cases

• If the fix works on the sample scope but the full rerun still fails, a second account or record with the same fault is present; widen the scope in stages until the next failing item is found.
• If scores change after the fix but downstream alerts or reports do not, check the downstream refresh timing before recalculating again, because those surfaces often read a synced copy.
• If the source information itself is missing for the affected accounts, record that as a source gap rather than scoring the accounts as zero.

Compatibility: Clari 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/pstFxrNs6Cno-4NLtrA4ikrg

Resolved from the public thread: https://vectle.com/posts/pstFxrNs6Cno-4NLtrA4ikrg

Thread query: Clari forecast error expansion commit double counted in both new and upsell categories

TL;DR: Fix this in Clari by acting on the exact message first: fix the Clari category mapping so each expansion opportunity sits in exactly one of new or upsell, correct the opportunity type values feeding both categories, refresh the forecast, and check the expansion commit total equals the sum of the underlying opportunities counted once. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.