usage signals missing from health score: data join failed

Not specified by the original author.

TL;DR

When a score component empties across many accounts at once, the join broke: keys changed format, the usage table's grain shifted from account-day to user-day, or late rows miss the scoring snapshot. Inspect the join with row counts on both sides and unmatched-key samples; joins confess quickly under counts.

usage signals missing from health score: data join failed

Use this when

• The usage component is zero or null for a broad set of accounts
• Usage dashboards outside the score look healthy
• A key, schema, or pipeline change touched either side of the join

Not for this skill when

• Only new accounts are missing, suggesting provisioning lag
• Usage itself is missing upstream, a pipeline problem not a join problem

Steps

1. Count rows and distinct account keys in the usage table and in the scoring input for the same window. Verify: the size of the unmatched population is quantified
2. Sample 20 unmatched keys from each side and compare formats character by character. Verify: the key mismatch (prefix, case, type, or id system) is visible
3. Check grain: confirm both sides aggregate to the same account and day grain before joining. Verify: any grain mismatch that fans out or drops rows is found
4. Fix the key mapping or grain, re-run the join, and compare component coverage before and after. Verify: usage components populate for the previously empty accounts
5. Add a join-coverage check (matched percentage) to the scoring run with an alert below threshold. Verify: the next join break stops the run loudly instead of scoring zeros

Variant phrasings

usage component empty in health score

A related phrasing for the same underlying problem.

join between usage and accounts failing

A related phrasing for the same underlying problem.

unmatched account keys in scoring

A related phrasing for the same underlying problem.

Compatibility: Compatibility: warehouse joins across product analytics, CRM account tables, and scoring models (dbt tests, SQL pipelines), current versions.

Why it happens

Joins fail silently by design: unmatched rows simply vanish. The tell is a component that empties broadly while its source table stays healthy. Counting both sides and reading raw unmatched keys turns the silent failure into a formatting fact.

Edge cases / pitfalls

• Inner versus left join choices decide whether a break zeroes scores or drops accounts entirely. Know which symptom you have before searching.
• Late-arriving usage needs a scoring delay or a restatement pass; a key fix will not cure a timing gap.
• Merged accounts legitimately produce many-to-one keys. Maintain the merge map as data, not as join conditions scattered in SQL.

Provenance

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

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

Thread query: usage signals missing from health score: data join failed

TL;DR: When a score component empties across many accounts at once, the join broke: keys changed format, the usage table's grain shifted from account-day to user-day, or late rows miss the scoring snapshot. Inspect the join with row counts on both sides and unmatched-key samples; joins confess quickly under counts.

Not specified by the original author.

TL;DR

The usage data moved and the score did not, so the break is between them: a sync job that skipped the account, a scoring run that read a stale snapshot, or a join key that stopped matching. Trace one affected account through the usage table, the sync log, and the score input snapshot to find which hop dropped it.

usage drop detected but health score not updated: sync failure

Use this when

• Usage tables show the drop but the health score is unchanged
• Other accounts updated in the same scoring run, or none did
• A sync or scoring job recently changed schedule or owner

Not for this skill when

• The score updated but support and NPS gains legitimately offset the usage loss
• Usage itself is wrong, which is an upstream pipeline problem

Steps

1. Take one affected account and record its usage values in the source table with timestamps. Verify: the source drop and its timestamp are documented
2. Check the sync job log for that account and run: succeeded, skipped, or failed with what reason. Verify: the account's sync outcome and any skip reason are known
3. Open the exact input snapshot the last scoring run used and find the account's row. Verify: the snapshot shows stale usage, a missing row, or current usage, which isolates the failing hop
4. Fix that hop (schedule, join key, or snapshot freshness), re-run the sync and scoring for the account. Verify: the health score moves to reflect the real usage drop
5. Add a freshness check comparing newest usage timestamp against newest score timestamp per account. Verify: staleness over the threshold alerts instead of silently scoring old data

Variant phrasings

usage changed but health score stale

A related phrasing for the same underlying problem.

health score sync not picking up usage

A related phrasing for the same underlying problem.

scoring job reading old snapshot

A related phrasing for the same underlying problem.

Compatibility: Compatibility: scheduled scoring pipelines (Airflow or cron-driven jobs, warehouse to CRM or Gainsight-style sync), current versions.

Why it happens

Health scores are only as fresh as their stalest input hop. Usage, sync, and scoring each look healthy in isolation while their handoff fails, so the diagnostic is a single-account trace across all three with timestamps at each hop.

Edge cases / pitfalls

• A scoring run that deliberately uses a weekly snapshot is not broken. Check the intended cadence before filing the sync as failed.
• Join keys often break only for renamed or merged accounts. Test the trace on a normal account as a control.
• Re-scoring history changes past scores. Snapshot the old scores before the corrective run.

Provenance

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

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

Thread query: usage drop detected but health score not updated: sync failure

TL;DR: The usage data moved and the score did not, so the break is between them: a sync job that skipped the account, a scoring run that read a stale snapshot, or a join key that stopped matching. Trace one affected account through the usage table, the sync log, and the score input snapshot to find which hop dropped it.

Not specified by the original author.

TL;DR

Fix this in Gainsight by acting on the exact message first: check Data Management import history first for the failed usage job, correct its error rows and re-import, and only then rerun the scorecard rule, because rerunning the score alone against a failed import recalculates from the same stale usage snapshot. 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 health score not recalculating after usage import fails

Use this when

• The operation in Gainsight fails with this exact message or symptom: how to fix Gainsight health score not recalculating after usage import fails.
• 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: check Data Management import history first for the failed usage job, correct its error rows and re-import, and only then rerun the scorecard rule, because rerunning the score alone against a failed import recalculates from the same stale usage snapshot. 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

The scorecard rule reads the last successful usage load, so a failed import leaves it calculating from old data no matter how many times the score itself is rerun.

Variant phrasings

how to fix Gainsight health score not recalculating after usage import fails

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 health score not recalculating after usage import 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_BF00LzDMb4lQpXgWE7eEtw

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

Thread query: how to fix Gainsight health score not recalculating after usage import fails error

TL;DR: Fix this in Gainsight by acting on the exact message first: check Data Management import history first for the failed usage job, correct its error rows and re-import, and only then rerun the scorecard rule, because rerunning the score alone against a failed import recalculates from the same stale usage snapshot. 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.