Understanding Freshdesk Errors in Hurree

If you're experiencing issues with your Freshdesk 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: Hurree was unable to verify your Freshdesk connection. This usually happens when your API key has been regenerated, your password has been changed, or access to Hurree has been revoked from within your Freshdesk account.

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

Explanation: You don't have permission to access this Freshdesk resource. Freshdesk permissions depend on your agent role and the ticket scope assigned to you, so you may be able to see some tickets or groups but not others.

How to solve: Check that your Freshdesk account has the necessary access rights for the data you're reporting on, or contact your administrator and ask them to review your agent role and ticket scope. Once the required access has been granted, refresh your connection and try retrieving the data again.

Explanation: The requested Freshdesk resource could not be found. This may occur if a ticket, contact, company, or group has been deleted, or if the reference is incorrect.

How to solve: Review the relevant Freshdesk account 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 the resource is in a conflicting state. This typically happens when the same record is being updated in two places at once, or when a ticket has changed status while the request was in progress.

How to solve: Review your data in Freshdesk for recent changes or duplicate entries, then try again. If the conflict continues, please contact our support team for assistance.

Explanation: Freshdesk restricts the number of requests that can be made within a given time period, and these limits vary depending on your Freshdesk plan. This error means that limit has been reached, usually because a large volume of data was requested at once.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you see this error frequently, consider reducing the number of Freshdesk widgets refreshing at the same time.

Explanation: An unexpected error occurred on Freshdesk's servers. This is not caused by any action on your part, and as the issue originates within Freshdesk'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: You may occasionally see 400: Bad Request, 405: Unsupported Accept Header, or 415: Unsupported Media Type. These indicate that something about the request sent to Freshdesk was invalid, incorrectly formatted, or used a format Freshdesk doesn't support; 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 Freshdesk 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.