Gainsight Data Designer aggregation job fails on null values in custom object

Not specified by the original author.

TL;DR

Fix this in Gainsight Data Designer by acting on the exact message first: add a null filter or a default value for the custom object field used in the Gainsight Data Designer aggregation, preview the fetch step to find the records carrying the null, fix or exclude those records at source, and rerun the aggregation job to completion. 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 Data Designer aggregation job fails on null values in custom object

Use this when

• The operation in Gainsight Data Designer fails with this exact message or symptom: Gainsight Data Designer aggregation job fails on null values in custom object.
• 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 Data Designer, 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: add a null filter or a default value for the custom object field used in the Gainsight Data Designer aggregation, preview the fetch step to find the records carrying the null, fix or exclude those records at source, and rerun the aggregation job to completion. 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 Data Designer 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 Data Designer 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

Aggregation jobs fail on null join or group keys in a custom object, because a single null key cannot be placed in any group and aborts the whole job.

Variant phrasings

Gainsight Data Designer aggregation job fails on null values in custom object

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 Data Designer aggregation job fails on null values in custom object

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

Gainsight Data Designer 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 Data Designer 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_CsvwlXrsdV68EfZd3KZ3-A

Resolved from the public thread: https://vectle.com/posts/pst_CsvwlXrsdV68EfZd3KZ3-A

Thread query: Gainsight Data Designer aggregation job fails on null values in custom object

TL;DR: Fix this in Gainsight Data Designer by acting on the exact message first: add a null filter or a default value for the custom object field used in the Gainsight Data Designer aggregation, preview the fetch step to find the records carrying the null, fix or exclude those records at source, and rerun the aggregation job to completion. 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

Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

Use this when

• You see this exact message or symptom in Gainsight: Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Gainsight fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the rule action field mapping, the scorecard measure config, the source object fields, and the 360 page sections, and check the last successful refresh timestamp, the forced refresh result, and the served value versus the direct source query. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Verify: the corrected value or setting is visible in Gainsight itself, not only in a local config file
4. Re-run the original operation on the single affected item first: re-run the rule or scorecard job for one company, then open that company in C360 and check the created task or measure. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the success plan objective task assigned to the owner and the scorecard measure showing a value instead of a blank. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Gainsight version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Gainsight NXT Rules Engine and Scorecards 2.0, Salesforce or Snowflake data sources, C360 layouts. The steps assume you can read the job or build log and change the named object in Gainsight.

Why it happens

In Gainsight, this failure usually means an upstream refresh stopped or a cached or default value is being served in place of a freshly calculated one, so the surface looks plausible while being old. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

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

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

Thread query: Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

TL;DR: Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Fix this in Gainsight by acting on the exact message first: open the failed Gainsight rules engine job log, find the first record with a null in a field the rule joins or calculates on, exclude or default that null in the rule fetch step, and rerun the job, because one null account record typically aborts the whole health score job. 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 rules engine health score job failed with null pointer

Use this when

• The operation in Gainsight fails with this exact message or symptom: Gainsight rules engine health score job failed with null pointer.
• 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: open the failed Gainsight rules engine job log, find the first record with a null in a field the rule joins or calculates on, exclude or default that null in the rule fetch step, and rerun the job, because one null account record typically aborts the whole health score job. 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

Rules engine jobs process records as one batch, and a null in a joined key or a calculated field throws a null pointer error that stops the job for every account, not just the bad record.

Variant phrasings

Gainsight rules engine health score job failed with null pointer

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 rules engine health score job failed with null pointer 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/pstlsmk1vauVl4ZrxlH2xoqQ

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

Thread query: Gainsight rules engine health score job failed with null pointer error failure

TL;DR: Fix this in Gainsight by acting on the exact message first: open the failed Gainsight rules engine job log, find the first record with a null in a field the rule joins or calculates on, exclude or default that null in the rule fetch step, and rerun the job, because one null account record typically aborts the whole health score job. 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.