Understanding Salesforce Errors in Hurree

If you're experiencing issues with your Salesforce widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree.

If you encounter an error that isn't covered below, please contact our support team for assistance.

Explanation: Your Salesforce session is no longer valid, so your widgets cannot retrieve updated data. This usually happens when your authorisation has expired, your password has been changed, or access to Hurree has been revoked from within your Salesforce org.

How to solve: Reconnect your Salesforce account through Hurree to restore access. Once reconnected, your widgets will begin updating again from the next scheduled sync.

Explanation: Access to this Salesforce resource has been refused. This can occur if your profile or permission set does not grant access to the relevant object or field, if access has been revoked, or if your org has exceeded its API request allowance; Salesforce applies a daily request limit per org and refuses further requests once it has been reached.

How to solve: Check that your Salesforce account has the necessary object and field permissions, or contact your administrator and ask them to review your profile and permission sets. If your permissions are correct and you have recently run a large number of requests, wait a moment and try again, as your org's API allowance may need time to reset.

Explanation: The requested Salesforce resource could not be found. This may occur if a record, report, or object such as a lead, account, contact, or opportunity has been deleted, or if the reference is incorrect.

How to solve: Review the relevant Salesforce org and verify that the record or data source still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

Explanation: The request could not be completed because it conflicts with the current state of the resource in Salesforce, for example, if the record has been updated by another process in the meantime.

How to solve: Review the relevant data in your Salesforce org and try again. If the conflict continues, please contact our support team for assistance.

Explanation: The Salesforce resource you're trying to access has been retired or permanently removed and is no longer available. This can also apply to older API versions that Salesforce has since retired.

How to solve: Update your widget settings to point to an active record or data source. If you believe the resource should still be available, please contact our support team, and we'll investigate.

Explanation: Salesforce encountered a routing error while processing your request. This originates within Salesforce's infrastructure and is not caused by any action on your part.

How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists, please contact our support team, and we'll investigate.

Explanation: An unexpected error occurred on Salesforce's servers. This is not caused by any action on your part, and as the issue originates within Salesforce's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Explanation: Salesforce is currently unavailable, most often due to maintenance or an unexpected outage on their side.

How to solve: Wait a few minutes and try again. Your widgets will update automatically once Salesforce is back online. If the outage appears to be prolonged, you can check Salesforce Trust for the status of your instance.

Explanation: You may occasionally see 502: Communication Error. This means Salesforce encountered a communication error while your request was being processed, and it is not caused by any action on your part.

How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists, please contact our support team for assistance.

Explanation: You may occasionally see one of the following less common errors: 400: Bad Request, 405: Method Not Supported, 412: Precondition Failed, 414: URI Too Long, 415: Unsupported Format, 428: Precondition Required, or 431: Headers Too Large. These indicate that something about the request sent to Salesforce was invalid, incorrectly formatted, too long, or missing a required condition; they are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If any of these errors persist, please contact our support team with the error name you're seeing, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your Salesforce widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.