Troubleshooting

This page shows the error messages generated in different situations where there are errors in the installation and configuration of the SlapFive Salesforce App.

NOTE: The SlapFive components embedded in the Salesforce App require all Salesforce users to have Third Party Cookies enabled in their browser. This is the default for all browsers except Safari.

Error Message or Condition	Cause and Resolution
"SlapFive API authenticating failed. Please contact your administrator." error appears within a SlapFive custom UI component.	In Named Credential, the API Base URL or API Key is not correct. See the Create Named Credential section and check that you copied your correct SlapFiveAPI Key into the API Key field and that the API Base URL field contains https://your_company_name.slapfive.com.
"Something went wrong." error appears within a SlapFive custom UI component.	In the SlapFive Custom Settings the API Base URL is blank or incorrect. See the Configure Custom Settings section and check that the API Base URL field contains https://your_company_name.slapfive.com.
Salesforce user sees the SlapFive login screen when trying to view a SlapFive Salesforce App component.	The Profile of the User doesn't have access to the SlapFive Connected App. See the Assign Permissions section and add the affected users to the SlapFive App Permission Sets.
Unauthorized endpoint, please check Setup->Security->Remote site settings. endpoint = ….	In the Remote Site Settings for SlapFive API, the Remote Site URL is blank or incorrect. See the Create a Remote Site section and check that the Remote Site URL field contains https://your_company_name.slapfive.com.
There is no board data with the matching field(s).	The API returns no records with matching field data. Make sure you have Boards defined in SlapFive that contain Companies with valid Matching Field data.
No SlapFive Boards appear in the Boards embedded list or when you click the View Case Studies button.	API returns no records when getting All data or searching with keyword. Make sure you have Boards defined in SlapFive with a Custom Field called Show in Salesforce, with a value of "Yes" or "yes".
"SlapFive container does not support for this type of record page." error when adding a SlapFive App component to a page layout.	You are attempting to put a SlapFive Salesforce App component on a page layout that is not supported. Components can be added to the Opportunity, Account and Contact page layouts.
"Single Sign-On Error. Error: Unable to resolve a request into a Service Provider." error when viewing SlapFive App components.	The Entity ID field on the SlapFive Connected App in Salesforce Setup is incorrect. See the Create Connected App section and check that the Entity ID field contains urn:auth0:slapfive:your_instance_name
"Connection failed. Action failed due to server error." error when connecting to Salesforce from your SlapFive Settings.	Workato is blocked in Salesforce. Go to Setup > Connected Apps OAuth Usage and unblock Workato.

Errors specific to older versions

Error Message or Condition	Cause and Resolution
"SlapFive API authenticating failed. Please contact your administrator." error appears within a SlapFive custom UI component.	In the SlapFive Custom Settings (version 3 and earlier) or in Named Credential (version 3.4 or later), the API Base URL or API Key is not correct. In version 3.4 only, the Profile of the User doesn't have the View Setup and Configuration permission checked. See the Assign Permissions section.
Matching field(s) is not configured.	Missing Custom Metadata Type configuration for SlapFive API matching fields.
One of Account fields in mapping field configuration does not exist.	Using incorrect Account field name in matching field configuration.
No record is found with the target Id.	Target Account Id or Opportunity Id does not exist.