Sync Troubleshooting
The following are answers to some common sync errors you may come across.
Error: Glance session data fails to sync / "Glance API Server Error: 666 - Invalid admin credentials"
Console: Lightning
Problem Description
If your Glance session data is failing to sync with your Salesforce org, check the "Glance sync history" tab and look for this error:
Remediation
-
Navigate to the Glance Company Settings tab. Scroll down to the Glance for Salesforce Users section and delete the admin user account.
-
Then navigate to the Glance User Settings tab and re-enter the admin's Glance username and password.
NOTE: This error will occur if the same Glance account is used in multiple Salesforce orgs. If session data needs to be synced to multiple orgs, use different Glance credentials for each org.
Error: Glance session data fails to sync / "Only Whitespace Content Allowed Before Start Tag and Not T"
Console: Lightning
Problem Description
If your Glance session data is failing to sync with your Salesforce org, check the "Glance sync history" tab and look for this error:
Remediation
-
Navigate to the Glance Company Settings tab. Scroll down to the Glance for Salesforce Users section and delete the admin user account.
-
Then navigate to the Glance User Settings tab and re-enter the admin's Glance username and password.
NOTE: This error will occur if the same Glance account is used in multiple Salesforce orgs. If session data needs to be synced to multiple orgs, use different Glance credentials for each org.
Date Range More Than 31 Days
Problem Description
This error message appears on the Glance sync history tab:
Glance API Server Error: 666 - date range cannot be more than 31 days
Remediation
When your sync has failed and it has failed for 30+ days, you will have to modify the sync settings to get it to back update all previous sessions.
- In Setup find Custom Settings, click "Manage" next to Glance Settings
- If no fields are shown under Default Organization Level Value, click New.
- Then set Max Sync Minutes to some limit. One week per batch is 10080 minutes ((7 * 24 * 60 = 10080). If customer hasn’t run a lot of sessions, this is typically a good setting. If they are like Intuit, you may want to look at 2 / 3 day batches vs. 7.
- Next navigate to the Glance Sync History and click Sync Now. Wait a few moments and then click Refresh. You should see the syncs updating.
Other examples:
Now: Max Sync Minutes is 180 = (1 * 3 * 60) = 3 hours
Maybe update: 60 = (1 * 1 * 60) = one hour
10 = 6 minutes
User Not Found
Problem Description
Sessions fail to sync for certain users. The Sync History tab shows a comment that says User not found:
Solution
- Confirm the user has an active Salesforce account.
- Confirm the user has a PUID when using the loginkey authentication method or SAML 2.0 . A PUID is required for all users using Glance for Salesforce.
- Confirm PUID matches between Salesforce and the Glance back end. Note that the sync matching is case sensitive for PUID, while SSO is not. This means that a Salesforce user with a case-mismatch in their PUID could successfully conduct Glance sessions but have the sync fail.
Duplicate Glance Session Objects Created
Problem Description
Instead of syncing data back to the Glance Session record that was created at session launch, the sync process creates a new Glance session with the same start time, session key, etc. and syncs the end time and duration to that new object.
In the screen shot below you can see the pairs of Glance Session records: each pair has the same start time, but only one has the end time/duration/Glance sync.
Remediation
This is caused by there being multiple Salesforce accounts with the same email address which was being used as the PUID by Glance. PUID needs to be a unique value across all users.