Ensure That All Tokens Are Mapped and Try Again Copilot Gainsight Error
Common Errors and Reasons
This article lists the mutual errors that might be encountered across Gainsight operations. It also specifies the possible causes and solutions that can resolve these errors.
Rules Engine Errors
Rule Configuration
Mutual errors you may encounter while edifice a report.
| Rule Configuration Error: Invalid Field. Possible permission effect... |
|---|
| Mistake: (Replace 10 with object name) Invalid Field. Possible permission issue. Message: A field with the api name ''on object with the api name 'X does not exist or access permissions are required. |
| Possible cause: Permissions on the field used as "Account Lookup". |
| Possible solution: Have users check their permissions to the field or object highlighted in the fault. Have their SFDC admin adjust permissions on profile or permission set as necessary. |
| Rule Configuration Error: Currency Field in rule does non... |
|---|
| Mistake: Currency Field in rule is does not respect proper values. |
| Possible crusade: Given an org having multi-currency enabled, the rule needs additional configuration. |
| Possible solution: Alter the aggregation of the field to SUM. |
| Rule Configuration Error: Output field labels - Id should be unique |
|---|
| Error: The labels for output fields inside a rule are not unique. |
| Possible cause: Output fields within a rule probable have conflicting labels. This could be because the labels were auto-generated with the same text. |
| Possible solution: Change ane of the labels to a unique proper name. |
| Rule Configuration Mistake: When a dataspace is selected, a small... |
|---|
| Mistake: When a dataspace is selected, a small spinning wheel does not go away. |
| Possible cause: Ids on the backend identifying a dataspace did non pass properly. |
| Possible solution: Contact support. |
| Rule Configuration Error: Do non see MDA object in Matrix... |
|---|
| Mistake: Do not run across MDA object in Matrix data object pull down. |
| Possible cause: Permission may not have been given or Business relationship ID Mapping is missing. |
| Possible solutions:
|
Execution Log Related
These errors can be constitute in any rule, by navigating toRule name > Execution History > Click on a Run History > View Logs.
| Execution Log Related Error: {"bulletin":"Your query request was running... |
|---|
| Error: {"message":"Your query request was running for besides long.","errorCode":"QUERY_TIMEOUT"} |
| Possible crusade: Besides many records on SFDC object making query run too long. |
| Possible solutions:
|
| Execution Log Related Mistake: Object blazon 'X_c' is not supported... |
|---|
| Error: (Replace" X" with Object Name) Object blazon 'X__c' is non supported. If y'all are attempting to utilise a custom object, be sure to append the '__c' afterwards the entity name. Please reference your WSDL or the describe scall for the appropriate names.","errorCode":"INVALID_TYPE"}] |
| Possible cause: Field that the rule is loading into, OAuth |
| Possible solution: Check Contour / Permissions Set to ensure proper permissions on that field within the object. |
| Execution Log Related Error: Logs given no fault... |
|---|
| Error: Logs given no error. Rule is Creating CTAs and Org has sync Job to SFDC Enabled |
| Possible cause: SFDC Org is lacking resources; typically occurs when Task object has triggers, workflow rules, validation rules and process builders enabled on the object. |
| Possible solution:Reduce amount of triggers, workflow rules, validation rules and process builders enabled on the object. |
| Execution Log Related Mistake: The number of records fetched... |
|---|
| Error: The number of records fetched from the source is more than the limit supported by Gainsight. The current limit is 300,000 rows of data. (Limit may modify) |
| Possible cause: Initial data fetch from rule setup exceeds Gainsight limits |
| Possible solutions:
|
Rule Results
These errors pertains to the Excel sheet that is sent from Gainsight through a failure run, manual run, or examination run. Navigate to the Failed Records tab in excel.
| Rule Results Error: X__c is zilch |
|---|
| Error: ( Replace X with Field Name) "X__c is null" |
| Possible cause: Rule is unable to process mapped field where source value is cypher. |
| Possible solution: Add filters to rule setup or criteria so rule does non include null values. |
| Rule Results Mistake: [STRING_TOO_LONG : ………. (max length=k)] |
|---|
| Error: [STRING_TOO_LONG : ………. (max length=chiliad)] |
| Possible cause: Data Value length of source text field is too long to mapped destination field. |
| Possible solution: Extend the field limit of the destination field. |
| Rule Results Error: UNABLE TO LOCK ROW |
|---|
| Error: UNABLE TO LOCK ROW. |
| Possible cause: Another SFDC process is using the tape and it cannot be modified by GS Dominion. |
| Possible solutions:
|
| Rule Results Fault: The account has not yet been synced... |
|---|
| Error: Scorecard two.0 Score does not ready score, and C360 Scorecard 2.0 Section shows "The account has not yet been synced to MDA." |
| Possible cause: Salesforce Connector is not enabled and synced. |
| Possible solution: Enable Salesforce Connector and sync. |
| Rule Results Error: Blank row at |
|---|
| Error: Blank row at. |
| Possible cause: Nothing Identifiers. |
| Possible solution: Apply filters to control nulls or replace nulls with proper data. |
C360 & Dashboard Errors
| C360 & Dashboard Fault: Unable to Edit Customer Stage... |
|---|
| Mistake: Unable to Edit Client Stage via Summary View. |
| Possible cause: Sharing Settings on "Account Public Read Only". |
| Possible solutions:
|
| C360 & Dashboard Error: UI_VIEW_QUERY_EXECUTION_FAILED |
|---|
| Error: UI_VIEW_QUERY_EXECUTION_FAILED. |
| Possible cause: Dashboard Study / UI VIew has a field with the special character "?". |
| Possible solution: Rename field without "?" and re-save UI. For Gainsight Reports, remove report and re add to dashboard. |
| C360 & Dashboard Mistake: Entire C360 Summary Fails... |
|---|
| Error: Entire C360 Summary Fails to Load. |
| Possible cause: Related Department saved without a selected written report. |
| Possible solution: If a section is added without a report, brand sure to remove the section. |
| C360 & Dashboard Mistake: Overall C360 Score not populating... |
|---|
| Error: Overall C360 Score not populating, doubling, non calculating. |
| Possible cause: Indistinguishable Scorecard entries on backend from change of configuration. |
| Possible solution: Contact Gainsight Support. |
Usage Information Errors
| Usage Data Error |
|---|
| Error: Duplicates being created from a rule. |
| Possible cause: Improper identifiers in rule. |
| Possible solution: Choose appropriate identifiers to update unique record. |
Cockpit Errors
Cockpit Configuration
| Cockpit Configuration Error: "Server Error" when attempting to add together link objects... |
|---|
| Error: "Server Error" when attempting to add link objects to employ in Telephone call to Actions. |
| Possible cause: N/A |
| Possible solution: Need a profile with "Modify all data permissions" and "Customize application" to link an object for Call to Deportment. |
| Cockpit Configuration Error: Email Assist does not say... |
|---|
| Error: Electronic mail Aid does not say "Sent Successfully". |
| Possible crusade: Email is in deny list or bounced. |
| Possible solution: Remove email from the deny list in Administration -> Email Configuration or ship it to a unlike email. |
Success Plan Errors/Limits
| Success Program Error/Limit |
|---|
| Error: Success Plan Criteria & Comment Limit results in unsuccessful export via report builder. |
| Possible cause: 32,767 characters for comments and 1,000 for Success Programme Criteria is the limit. |
| Possible solution: Readjust comments or Success Plan text to be under the limits. |
Journeying Orchestrator Errors
Participant Load via CSV
| Participant Load via CSV Error |
|---|
| Mistake: Schedule could not be created with the selected participants. This can happen when email addresses and/or contact records are missing. |
| Possible cause:Contact being loaded are not valid SFDC Contacts. |
| Possible solution: Load proper Contact IDs instead of emails. |
Token Configuration Error
| Token Misconfiguration |
|---|
| Error: Outreach Execution failed: Outreach failed because of token misconfiguration. |
| Possible cause:Email Template that was added to the outreach was modified, but the modified outreach was non added to the outreach before publishing. |
| Possible solution: Remove existing template from outreach. Add a different template, relieve the outreach, and so re-add together the modified template, save the outreach, and attempt publishing it once again. |
E-mail Templates
| Electronic mail Templates Error |
|---|
| Mistake: Text format of tokens looks dissimilar than rest of template. |
| Possible cause: Token created by the token push button. |
| Possible solution: Create text offset, highlight, so create token. |
Test Email
| Examination Email Error |
|---|
| Fault: Date time format displays as epoch time in test email |
| Possible cause: Session Settings configuration under Setup. |
| Possible solution: Uncheck the following settings nether Setup:
|
S3 Errors
| S3 Error:"Unable to parse number: X at... |
|---|
| Error: Unable to parse number: 10 at row number two. |
| Possible crusade: Value "X" is unable to be parsed since the field receiving data is expecting a number. |
| Possible solutions:
|
| S3 Fault: Data Non Loading in New MDA Object |
|---|
| Error: Data Not Loading in New MDA Object. |
| Possible cause: Column has leading spaces. |
| Possible solutions:
|
Cyberduck Errors
| Cyberduck Fault |
|---|
| Error: Directory Listing Error. |
| Possible cause: Wrong Path being used. |
| Possible solution: Copy the file path from gstext forwards. |
Miscellaneous Errors
| Miscellaneous Error: Error parsing json response... |
|---|
| Error: Status: Request failed. Message: Fault parsing json response 'Unexpected token <' Logged in?. |
| Possible cause: Field has been removed from MDA that the Rule was referencing. |
| Possible solution: Rule should have removed the missing tokens, if token has been re-added in MDA, re-map the rule for affected field. |
| Miscellaneous Error: Tenant not notwithstanding configured... |
|---|
| Mistake: Tenant not yet configured. Contact Gainsight Admin. |
| Possible cause: If creating a new sandbox or new org, MDA Services may not take been enabled yet. |
| Possible solutions:
|
| Miscellaneous Error: "statusCode": 200,"type": "rpc",... |
|---|
| Error: { "statusCode": 200, "type": "rpc", "tid": 18, "ref": simulated, "action": "JBCXM.WorkFlowBroker", "method": "workFlowRequestBroker", "outcome": { "dataObj": simulated, "errCode": "", "errMsg": "invalid ID field: Gainsight User", "success": simulated }, "condition": true } |
| Possible crusade: Probable User State Preservation is not working properly, need script from support. |
| Possible solution: Rule should have removed the missing tokens, if token has been re-added in MDA, re-map the dominion for afflicted field. |
Source: https://support.gainsight.com/SFDC_Edition/Administration_and_Permissions/General_Administration/Common_Errors_and_Reasons
0 Response to "Ensure That All Tokens Are Mapped and Try Again Copilot Gainsight Error"
Post a Comment