Gainsight rule execution failed SFDC SOQL query timeout: health scores

Not specified by the original author.

TL;DR

Split the rule before you tune anything else. A Gainsight rule that runs one wide SOQL query across enterprise accounts, contacts, and usage objects will time out in Salesforce long before Gainsight scoring logic is at fault. Narrow the query with selective filters and a shorter window, split the rule by segment, fetch in stages into Gainsight objects, and the same health scores calculate on schedule.

Gainsight rule execution failed SFDC SOQL query timeout: health scores not recalculated for enterprise accounts

Use this when

• The Gainsight rule execution history shows a Salesforce query timeout as the failure reason
• Smaller segments or manual narrow runs of the same rule succeed
• The rule joins several large Salesforce objects or scans years of activity history

Not for this skill when

• The rule fails instantly with a field or object permission error, which is an access problem, not a timeout
• Salesforce itself is in an incident window affecting all integrations

Steps

1. Open the failed run in Gainsight Rules Engine execution history and capture the exact step, query, and timeout message, plus how long it ran before failing. Rules often chain several fetches, and only one step usually times out while the rest pass, so do not rewrite the healthy steps. Verify: the failing fetch step and its query shape are identified
2. Measure the Salesforce side. Run a comparable count in Salesforce or a query tool for the objects involved, filtered the way the rule filters them today. Enterprise account sets with unfiltered activity, task, or usage history are the usual volume bombs, especially where the filter field is not indexed or selective, such as a free-text or formula field. Verify: the row volumes per object and the non-selective filter are named
3. Redesign the fetch in stages. Pull accounts first with a selective filter such as record type, active contract status, and a bounded last-modified window, load them to a Gainsight custom object, then fetch related usage and activity only for those account ids in a second rule or step. Staged fetches turn one giant join into several small indexed lookups. Verify: the staged rule processes the same account set with each fetch returning in a fraction of the timeout limit
4. Split execution by segment or region if one tenant still runs hot, and stagger the rule schedule away from other heavy Salesforce jobs such as backups, other integrations, and the nightly sync. Salesforce timeouts are often shared-tenancy timing, so a two hour schedule shift can be a real fix, not a workaround. Verify: each segment rule completes inside its window across three consecutive scheduled runs
5. Re-run the full health score calculation for the enterprise accounts that missed scoring, and compare a sample of twenty accounts against hand-checked Salesforce and usage values so a narrowed filter did not quietly drop accounts from scoring. Verify: sampled scores match hand checks and the scored account count equals the eligible enterprise count
6. Add a rule duration alert in Gainsight that warns when a run passes roughly seventy percent of the historical timeout zone, so the next growth in data volume shows up as a warning week instead of a silent scoring gap for your largest accounts. Verify: the duration alert exists and fires on a test long-running rule

Why it happens

Salesforce enforces synchronous query timeouts to protect shared resources, and Gainsight rules inherit that limit through the connector. Rule authors build logic against a smaller data set, then enterprise activity and usage history grow until the same query plan crosses the timeout. Because the rule fails as a unit, no scores update, and the failure looks like a Gainsight outage when it is really one unselective query.

Compatibility: Gainsight Rules Engine including Bionic Rules, Salesforce SOQL through the Gainsight connector, and Salesforce selective query and indexing guidance, current versions.

Variants and edge cases

Gainsight bionic rule SOQL timeout enterprise

['The Bionic Rules phrasing for the same shape. The fix is still query shape and staging, not retries, because a timed-out query retried unchanged times out again with more load.']

Salesforce query timeout Gainsight health score stale

['The symptom-first phrasing, where CS notices stale enterprise scores. Work backwards from score freshness per segment to the specific rule run that failed.']

Gainsight rule fetch step failing large accounts

['The step-level variant. Use execution history to isolate the fetch, because transformation and action steps in the same rule are usually innocent.']

Edge cases to work through before you close the incident:

• Formula fields and fields with leading wildcard text filters cannot be made selective by indexing. Change the filter design, not only the schedule.
• Custom indexes in Salesforce need a support case and a real query plan justification. Stage and split first, they solve most cases without one.
• When you split rules by segment, guard against overlap double-scoring an account. Keep one authoritative segment field and log which rule scored each account.

Provenance

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

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

Thread query: Gainsight rule execution failed SFDC SOQL query timeout: health scores not recalculated for enterprise accounts

TL;DR: Split the rule before you tune anything else. A Gainsight rule that runs one wide SOQL query across enterprise accounts, contacts, and usage objects will time out in Salesforce long before Gainsight scoring logic is at fault. Narrow the query with selective filters and a shorter window, split the rule by segment, fetch in stages into Gainsight objects, and the same health scores calculate on schedule.

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: run the rule in preview on a small account set and widen it until the failing record appears, fix that record missing company or usage link in the source, add a null check filter at the start of the rule, and schedule the full job again only after a clean preview. 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 rules engine health score job failed with null pointer

Use this when

• The operation in Gainsight fails with this exact message or symptom: how to fix 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: run the rule in preview on a small account set and widen it until the failing record appears, fix that record missing company or usage link in the source, add a null check filter at the start of the rule, and schedule the full job again only after a clean preview. 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

Previewing in widening slices isolates the single record causing the null pointer failure far faster than reading the full job log, and a fetch filter prevents the same record class from aborting future runs.

Variant phrasings

how to fix 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 - how to fix Gainsight rules engine health score job failed with null pointer 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_vfy0JDYljBV1wt0wt25Huw

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

Thread query: how to fix Gainsight rules engine health score job failed with null pointer fails error

TL;DR: Fix this in Gainsight by acting on the exact message first: run the rule in preview on a small account set and widen it until the failing record appears, fix that record missing company or usage link in the source, add a null check filter at the start of the rule, and schedule the full job again only after a clean preview. 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.