how to fix Totango segmentation error subsidiary accounts excluded fro

Not specified by the original author.

TL;DR

Fix this in Totango by acting on the exact message first: fix the Totango segment rule so subsidiary companies roll up to the parent for the rollup view, check the parent company setting and hierarchy sync, add the missing subsidiaries to the segment, and verify the parent total now includes a named subsidiary. 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.

how to fix Totango segmentation error subsidiary accounts excluded from parent rollup view

Use this when

• The operation in Totango fails with this exact message or symptom: how to fix Totango segmentation error subsidiary accounts excluded from parent rollup view.
• 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 Totango, 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 Totango segment rule so subsidiary companies roll up to the parent for the rollup view, check the parent company setting and hierarchy sync, add the missing subsidiaries to the segment, and verify the parent total now includes a named subsidiary. 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 Totango 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 Totango 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

Segment rules that match only the parent company record silently drop subsidiaries linked in the hierarchy but not matched by the segment criteria themselves.

Variant phrasings

how to fix Totango segmentation error subsidiary accounts excluded from parent rollup view

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 - how to fix Totango segmentation error subsidiary accounts excluded from parent rollup view

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

Totango 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: Totango 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_5ItEcJLm22cmKuExjLmQXA

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

Thread query: how to fix Totango segmentation error subsidiary accounts excluded from parent rollup view

TL;DR: Fix this in Totango by acting on the exact message first: fix the Totango segment rule so subsidiary companies roll up to the parent for the rollup view, check the parent company setting and hierarchy sync, add the missing subsidiaries to the segment, and verify the parent total now includes a named subsidiary. 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.

Not specified by the original author.

TL;DR

Fix this in Totango by acting on the exact message first: in Totango, find accounts belonging to two segments included in the same portfolio average, deduplicate the average by account rather than by segment membership, fix overlapping segment criteria if the overlap is unintended, and recalculate the portfolio average from unique accounts. 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.

Totango segment health error - accounts counted twice in portfolio average

Use this when

• The operation in Totango fails with this exact message or symptom: Totango segment health error - accounts counted twice in portfolio average.
• The same failure repeats on retry with unchanged inputs.
• Scoring, alerting or routing 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 Totango, and copy the full message plus the account, measure 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: in Totango, find accounts belonging to two segments included in the same portfolio average, deduplicate the average by account rather than by segment membership, fix overlapping segment criteria if the overlap is unintended, and recalculate the portfolio average from unique accounts. Verify: the smallest failing scope now completes, or the named account, measure or job behaves as the fix predicts.
3. Check the neighbouring accounts, measures or jobs that share the same config, schema or credential, 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 Totango 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 Totango 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

Segment based averages count memberships, not accounts, so an account in two included segments enters the average twice and skews it toward that account score.

Variant phrasings

Totango segment health error - accounts counted twice in portfolio average

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 - Totango segment health error accounts counted twice in portfolio average error failure

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

Totango 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 data itself is missing for the affected accounts, record that as a data gap rather than scoring the accounts as zero.

Compatibility: Totango 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_RxbJBmhGaj4QtTwqHRvHag

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

Thread query: Totango segment health error accounts counted twice in portfolio average error failure

TL;DR: Fix this in Totango by acting on the exact message first: in Totango, find accounts belonging to two segments included in the same portfolio average, deduplicate the average by account rather than by segment membership, fix overlapping segment criteria if the overlap is unintended, and recalculate the portfolio average from unique accounts. 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.

Not specified by the original author.

TL;DR

Fix this in Totango by acting on the exact message first: list the overlapping accounts between the segments in the rollup, decide whether the overlap is a criteria error or a reporting error, correct the segment definitions or switch the portfolio metric to distinct accounts, and verify the denominator equals the unique account count. 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.

how to fix Totango segment health error accounts counted twice in portfolio average

Use this when

• The operation in Totango fails with this exact message or symptom: how to fix Totango segment health error accounts counted twice in portfolio average.
• The same failure repeats on retry with unchanged inputs.
• Scoring, alerting or routing 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 Totango, and copy the full message plus the account, measure 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: list the overlapping accounts between the segments in the rollup, decide whether the overlap is a criteria error or a reporting error, correct the segment definitions or switch the portfolio metric to distinct accounts, and verify the denominator equals the unique account count. Verify: the smallest failing scope now completes, or the named account, measure or job behaves as the fix predicts.
3. Check the neighbouring accounts, measures or jobs that share the same config, schema or credential, 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 Totango 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 Totango 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

The denominator is the tell: when it exceeds the number of real accounts, double counting is certain, and fixing either segment criteria or the distinct count restores the average.

Variant phrasings

how to fix Totango segment health error accounts counted twice in portfolio average

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 - how to fix Totango segment health error accounts counted twice in portfolio average fails error

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

Totango 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 data itself is missing for the affected accounts, record that as a data gap rather than scoring the accounts as zero.

Compatibility: Totango 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_RZGQSrcY46kESzZSU9FWtQ

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

Thread query: how to fix Totango segment health error accounts counted twice in portfolio average fails error

TL;DR: Fix this in Totango by acting on the exact message first: list the overlapping accounts between the segments in the rollup, decide whether the overlap is a criteria error or a reporting error, correct the segment definitions or switch the portfolio metric to distinct accounts, and verify the denominator equals the unique account count. 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.