customer health score wrong after duplicate accounts merged in CRM err

Not specified by the original author.

TL;DR

Fix this in customer health score by acting on the exact message first: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. 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.

customer health score wrong after duplicate accounts merged in CRM

Use this when

• The operation in customer health score fails with this exact message or symptom: customer health score wrong after duplicate accounts merged in CRM.
• 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: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. 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

The score keeps reading whichever record id it was bound to, and a merge that retires that id or drops its history leaves the survivor scored from a partial or empty past.

Variant phrasings

customer health score wrong after duplicate accounts merged in CRM

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 - customer health score wrong after duplicate accounts merged in CRM error failure

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/pstdP59FoX5ZJLd87BvGY6_w

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

Thread query: customer health score wrong after duplicate accounts merged in CRM error failure

TL;DR: Fix this in customer health score by acting on the exact message first: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. 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: audit the merge mapping for the affected accounts, confirm the health platform now keys on the surviving CRM id, re-run the account sync so the duplicate is removed there too, and recalculate, checking the score uses usage from both pre-merge records. 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 wrong after duplicate accounts merged in CRM

Use this when

• The operation in customer health score fails with this exact message or symptom: how to fix customer health score wrong after duplicate accounts merged in CRM.
• 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: audit the merge mapping for the affected accounts, confirm the health platform now keys on the surviving CRM id, re-run the account sync so the duplicate is removed there too, and recalculate, checking the score uses usage from both pre-merge records. 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

Health platforms key scores by external account id, so until the sync propagates the merge they score the retired duplicate and the survivor separately with split histories.

Variant phrasings

how to fix customer health score wrong after duplicate accounts merged in CRM

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 wrong after duplicate accounts merged in CRM 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_XI9joZFRHH0gshavPUFh4g

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

Thread query: how to fix customer health score wrong after duplicate accounts merged in CRM fails error

TL;DR: Fix this in customer health score by acting on the exact message first: audit the merge mapping for the affected accounts, confirm the health platform now keys on the surviving CRM id, re-run the account sync so the duplicate is removed there too, and recalculate, checking the score uses usage from both pre-merge records. 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 duplicate merge agent workflow by acting on the exact message first: list the measures actually present on both duplicate records, merge only measures in that list, and flag any measure the agent expects but neither record has as a mapping question rather than inventing its combined value. 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.

agent hallucinating scorecard measure not in source data for merge duplicate account health records

Use this when

• The operation in duplicate merge agent workflow fails with this exact message or symptom: agent hallucinating scorecard measure not in source data for merge duplicate account health records.
• 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 duplicate merge agent workflow, 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 measures actually present on both duplicate records, merge only measures in that list, and flag any measure the agent expects but neither record has as a mapping question rather than inventing its combined value. 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 duplicate merge agent workflow 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 duplicate merge agent workflow 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 agent working from a standard scorecard template assumes measures the duplicates may not carry, and inventing a combined value for a missing measure corrupts the survivor score.

Variant phrasings

agent hallucinating scorecard measure not in source data for merge duplicate account health records

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 - agent hallucinating scorecard measure not in source data for merge duplicate account health records error hallucination failure

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

duplicate merge agent workflow 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: duplicate merge agent workflow 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/pst4pJhuUqSuq7j6ymoz5KPw

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

Thread query: agent hallucinating scorecard measure not in source data for merge duplicate account health records error hallucination failure

TL;DR: Fix this in duplicate merge agent workflow by acting on the exact message first: list the measures actually present on both duplicate records, merge only measures in that list, and flag any measure the agent expects but neither record has as a mapping question rather than inventing its combined value. 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.