/ /

Troubleshooting & FAQs

Updated 23 days ago

For issues common to all Enterprise Search connectors, such as sync status, authentication basics, throttling, and search visibility, see Troubleshooting - Enterprise Search Connectors.

Gainsight-specific issues

Connection test fails when saving the source

Symptoms

  • The source cannot be saved, or the first sync fails immediately with an authentication error.

Possible causes

  • The instance domain is wrong, for example acme was entered when the tenant is acme.us2.

  • The OAuth client ID or secret was copied incorrectly, or the secret was regenerated more than about 24 hours ago and the old one is still saved in Simpplr.

  • The Gainsight API connection has been deleted or disabled in Connectors 2.0.

Resolution

  1. Open Gainsight and copy the address from the browser. Enter everything before .gainsightcloud.com, for example acme.us2. If your tenant uses a vanity domain, enter the full host.

  2. In Gainsight, go to Administration → Integrations -> Connectors 2.0, open the Simpplr connection, and confirm it still exists and uses OAuth.

  3. If you are unsure of the secret, select Re-Generate Secret, then paste the new client ID and secret into the Simpplr source and save.

Sync fails with "The Gainsight company filter could not be applied"

Symptoms

  • The sync fails and the message lists company names or IDs that were not found, or names that match more than one company.

Possible causes

  • A company name in the filter does not exactly match the name in Gainsight, including spelling, spacing, and punctuation.

  • Two or more companies share the same name.

  • A company was deleted or merged in Gainsight, so its ID no longer exists.

  • A Customer 360 URL was pasted without the company ID in it.

Resolution

  1. For each entry listed in the message, open the company in Gainsight Customer 360.

  2. Copy the company ID from the Customer 360 URL, or copy the full Customer 360 URL, and replace the entry in the filter.

  3. Remove entries for companies that no longer exist.

  4. Save and run Sync now.

Sync fails because both company include and exclude are set

Symptoms

  • The sync fails with a message that the company include and exclude filters are mutually exclusive.

Possible causes

  • Entries were added to both the include and the exclude company filter.

Resolution

  1. Keep only one of the two filters. Use include to index only named companies, or exclude to index everything except named companies.

  2. Save and run Sync now.

Sync fails with "read zero records across every enabled object type"

Symptoms

  • The first full sync, or a later full sync, fails and no Gainsight results appear.

Possible causes

  • The filters exclude everything. For example, a company include filter lists companies that have no records within the document age window.

  • The Gainsight tenant has no data in any enabled object type.

Resolution

  1. Review the document age, object types, and company filters, and widen them.

  2. Save and run Sync now.

Incremental sync fails with "Please perform a full sync"

Symptoms

  • Hourly syncs fail with a message asking for a full sync.

Possible causes

  • No full sync has completed successfully since the source was added.

Resolution

  1. Run Sync now and wait for it to complete.

  2. If the full sync fails, resolve its error using the sections above.

A user cannot see Gainsight results

Symptoms

  • Some users get no Gainsight results or autocomplete suggestions, while other users do.

Possible causes

  • The user is not an active internal user in Gainsight, or has no email address in Gainsight.

  • The user's email in Gainsight differs from their email in Simpplr.

  • The user was added to Gainsight recently and the daily user sync has not run yet.

  • The user is outside the Audience configured for the source.

Resolution

  1. In Gainsight User Management, confirm the user is active, internal, and has the same email as in Simpplr.

  2. Check the source's Audience in the Admin Panel.

  3. Wait for the next daily user sync, which runs at 09:00 UTC.

A deleted Company or Relationship still appears in search

Symptoms

  • A company or relationship that was deleted in Gainsight still shows up in Simpplr search.

Possible causes

  • Company and Relationship deletions are only guaranteed to be removed by the weekly full sync.

Resolution

  1. Wait for the weekly full sync on Monday, or run Sync now.

FAQs

For general questions that apply to all connectors, see Troubleshooting - Enterprise Search Connectors and Data & Security - Enterprise Search Connectors.

Does the connector sync access control permissions?

No. Gainsight does not expose per-record permissions through its API. Any Simpplr user who matches an active internal Gainsight user can find every indexed record. Use object type filters, company filters, and Audiences to limit what is searchable and by whom.

Can we keep Timeline notes out of search?

Yes. Turn off Timeline Activity in the object type filter, then click Save and Sync. This runs a full sync and removes that content.

Can Simpplr change anything in Gainsight?

No. The connector only reads. Gainsight does not let the OAuth credential be limited to read-only, so read-only behaviour is enforced by Simpplr.

Why does a task open its CTA?

Gainsight has no standalone page for a task. Tasks are shown inside their parent CTA in Cockpit.

Are attachments indexed?

No. Files attached to timeline activities or other records are not indexed.

How quickly do changes in Gainsight appear in search?

New and changed records appear within about an hour. Deleted Timeline Activities, CTAs, Tasks, and Success Plans are removed within about an hour. Deleted Companies and Relationships are removed by the weekly full sync.

How quickly does a deactivated Gainsight user lose access?

After the next daily user sync.

Was this article helpful?
Subscribe to receive updates on this article