usage drop detected but health score not updated: sync failure

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 warehouse usage export scraper by acting on the exact message first: check the warehouse usage export the scraper requested, confirm its date window and schema still return rows in a direct query, fix the export query if the schema moved, and fall back to a direct warehouse export when the scraped export stays empty. 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.

scraper failed on warehouse usage export returning empty results for syncing Segment traits error scraping failure

Use this when

• The operation in warehouse usage export scraper fails with this exact message or symptom: scraper failed on warehouse usage export returning empty results for syncing Segment traits error scraping failure.
• 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 warehouse usage export scraper, 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 the warehouse usage export the scraper requested, confirm its date window and schema still return rows in a direct query, fix the export query if the schema moved, and fall back to a direct warehouse export when the scraped export stays empty. 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 warehouse usage export scraper 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 warehouse usage export scraper 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

An empty scraped export usually means the underlying query window or schema changed, not that no usage exists to sync traits from.

Variant phrasings

scraper failed on warehouse usage export returning empty results for syncing Segment traits error scraping failure

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 - scraper failed on warehouse usage export returning empty results for syncing Segment traits error scraping failure

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

warehouse usage export scraper 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: warehouse usage export scraper 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_TvejVbdxrTQztkspjEuoFg

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

Thread query: scraper failed on warehouse usage export returning empty results for syncing Segment traits error scraping failure

TL;DR: Fix this in warehouse usage export scraper by acting on the exact message first: check the warehouse usage export the scraper requested, confirm its date window and schema still return rows in a direct query, fix the export query if the schema moved, and fall back to a direct warehouse export when the scraped export stays empty. 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 customer health score by acting on the exact message first: open the failed Salesforce sync log, find the accounts whose health inputs failed to map, fix the field mapping or record type mismatch named in the log, rerun the sync for those accounts only, and recalculate once their usage fields are non-zero again. 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 customer health score dropped to zero after Salesforce sync fails

Use this when

• The operation in customer health score fails with this exact message or symptom: how to fix customer health score dropped to zero after Salesforce sync 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 customer health score, 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 failed Salesforce sync log, find the accounts whose health inputs failed to map, fix the field mapping or record type mismatch named in the log, rerun the sync for those accounts only, and recalculate once their usage fields are non-zero again. 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 customer health score 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 customer health score 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 the Salesforce sync fails partway, health inputs for the unprocessed accounts stay at their cleared staging values, which the score reads as zero usage.

Variant phrasings

how to fix customer health score dropped to zero after Salesforce sync 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 customer health score dropped to zero after Salesforce sync fails error

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

customer health score 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: customer health score 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_h3rZCFUW93CHOhmwceqfXA

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

Thread query: how to fix customer health score dropped to zero after Salesforce sync fails error

TL;DR: Fix this in customer health score by acting on the exact message first: open the failed Salesforce sync log, find the accounts whose health inputs failed to map, fix the field mapping or record type mismatch named in the log, rerun the sync for those accounts only, and recalculate once their usage fields are non-zero again. 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.