Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color

Not specified by the original author.

TL;DR

Fix this in Gainsight Scorecard 2.0 by acting on the exact message first: open the Gainsight Scorecard 2.0 grade settings, make the custom grade ranges contiguous with one owner for each boundary score, republish the scorecard, and verify sample scores at each boundary show the colour of the grade they fall in. 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.

Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color

Use this when

• The operation in Gainsight Scorecard 2.0 fails with this exact message or symptom: Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color.
• The same failure repeats on retry with unchanged inputs.
• Health 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 Gainsight Scorecard 2.0, 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: open the Gainsight Scorecard 2.0 grade settings, make the custom grade ranges contiguous with one owner for each boundary score, republish the scorecard, and verify sample scores at each boundary show the colour of the grade they fall in. 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 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 Gainsight Scorecard 2.0 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 Gainsight Scorecard 2.0 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

Scorecard grades are evaluated from the published grade config, and overlapping or gapped custom ranges leave boundary scores coloured by whichever grade the renderer reaches first.

Variant phrasings

Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color

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 - Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color

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

Gainsight Scorecard 2.0 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: Gainsight Scorecard 2.0 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_N4lxGJIbpFqhFKcpIMSYnQ

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

Thread query: Gainsight Scorecard 2.0 grade thresholds ignored custom range shows wrong color

TL;DR: Fix this in Gainsight Scorecard 2.0 by acting on the exact message first: open the Gainsight Scorecard 2.0 grade settings, make the custom grade ranges contiguous with one owner for each boundary score, republish the scorecard, and verify sample scores at each boundary show the colour of the grade they fall in. 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 Gainsight by acting on the exact message first: compare the C360 score and the report score field by field, because C360 shows the live scorecard value while reports often read a synced or snapshot field, align both to the same scorecard and as-of date, and refresh the report source before treating either number as wrong. 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.

Gainsight C360 health score mismatch with report score for same account

Use this when

• The operation in Gainsight fails with this exact message or symptom: Gainsight C360 health score mismatch with report score for same account.
• 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 Gainsight, 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: compare the C360 score and the report score field by field, because C360 shows the live scorecard value while reports often read a synced or snapshot field, align both to the same scorecard and as-of date, and refresh the report source before treating either number as wrong. 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 Gainsight 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 Gainsight 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

C360 and reports read the score from different stores with different refresh times, so a mismatch is usually a timing or source difference rather than two different calculations.

Variant phrasings

Gainsight C360 health score mismatch with report score for same account

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 - Gainsight C360 health score mismatch with report score for same account error failure

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

Gainsight 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: Gainsight 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_OUzpkeWj8gnN8JW9bY5nyg

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

Thread query: Gainsight C360 health score mismatch with report score for same account error failure

TL;DR: Fix this in Gainsight by acting on the exact message first: compare the C360 score and the report score field by field, because C360 shows the live scorecard value while reports often read a synced or snapshot field, align both to the same scorecard and as-of date, and refresh the report source before treating either number as wrong. 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 Gainsight by acting on the exact message first: pick one mismatched account, note the calculation timestamps shown in C360 and in the report, rerun the sync that feeds the report, and if they still differ check for two scorecards with similar names where C360 uses one and the report uses the other, then standardise on one. 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 Gainsight C360 health score mismatch with report score for same account

Use this when

• The operation in Gainsight fails with this exact message or symptom: how to fix Gainsight C360 health score mismatch with report score for same account.
• 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 Gainsight, 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: pick one mismatched account, note the calculation timestamps shown in C360 and in the report, rerun the sync that feeds the report, and if they still differ check for two scorecards with similar names where C360 uses one and the report uses the other, then standardise on one. 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 Gainsight 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 Gainsight 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

Duplicate or versioned scorecards let two surfaces legitimately show different scores for the same account because each surface points at a different scorecard definition.

Variant phrasings

how to fix Gainsight C360 health score mismatch with report score for same account

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 Gainsight C360 health score mismatch with report score for same account fails error

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

Gainsight 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: Gainsight 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_6AtvCLmHQsTv01Mv5vwPIg

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

Thread query: how to fix Gainsight C360 health score mismatch with report score for same account fails error

TL;DR: Fix this in Gainsight by acting on the exact message first: pick one mismatched account, note the calculation timestamps shown in C360 and in the report, rerun the sync that feeds the report, and if they still differ check for two scorecards with similar names where C360 uses one and the report uses the other, then standardise on one. 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.