Understanding Zendesk Errors in Hurree

If you're experiencing issues with your Zendesk 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: Zendesk processed the request successfully but returned no data. This is often expected, for example, if there is no ticket or user activity in the selected date range, or the resource is empty.

How to solve: Review the relevant Zendesk account and confirm whether data should be present for the period or resource you're reporting on. If you believe data is missing, try widening your widget's date range. If the issue persists, please contact our support team.

Explanation: The credentials used to connect your Zendesk account are no longer valid or have been revoked. Zendesk uses API credentials to verify your identity, and if these have been regenerated or removed, your widgets will stop retrieving data.

How to solve: Reconnect your Zendesk account via Hurree to restore access. Reconnecting re-establishes the connection with valid credentials, and your widgets should begin retrieving data again. If the issue continues after reconnecting, please contact our support team for assistance.

Explanation: Your Zendesk subscription requires a payment update before this request can be completed. Zendesk restricts API access when an account has outstanding billing issues.

How to solve: Review your billing settings in Zendesk and update your payment details, then try again. If the error persists once your billing is up to date, please contact our support team.

Explanation: You don't have permission to access this Zendesk resource. This can occur if your user role has changed, access has been revoked, or you have not been granted the appropriate level of access within Zendesk.

How to solve: Check that your Zendesk account has the necessary access rights, or contact your administrator and ask them to review your permissions. Once the required access has been granted, refresh your connection and try retrieving the data again.

Explanation: The requested Zendesk resource could not be found. This may occur if a ticket, user, organisation, view, or other record has been deleted or merged, or if the reference is incorrect.

How to solve: Review the relevant Zendesk account and verify that the resource 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 Zendesk, for example, if the record has been updated by another process in the meantime.

How to solve: Review the relevant data in your Zendesk account and try again. If the conflict continues, please contact our support team.

Explanation: The requested Zendesk resource is no longer available. It may have expired, or the referenced contact or deal may no longer exist.

How to solve: Unavailable resources cannot be restored through the connection. To continue reporting on Zendesk data, update your widget settings to use a different record or data source within your account.

Explanation: The data provided with this request could not be processed due to missing or invalid fields, meaning Zendesk could not complete it as expected.

How to solve: Check that all fields in your integration settings are correctly filled in and try again. If the issue persists, please contact our support team.

Explanation: Zendesk restricts the number of requests allowed within a given time window, and if your connected widgets are pulling data at a high frequency, this limit may occasionally be reached.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you are consistently hitting this limit, please contact our support team so we can review your connector configuration.

Explanation: An unexpected error occurred on Zendesk's servers. This is not caused by any action on your part, and as the issue originates within Zendesk'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: Zendesk is currently unavailable due to a temporary service disruption or maintenance on their platform.

How to solve: Wait a few minutes before trying again. Temporary outages are usually resolved automatically by Zendesk. If the issue persists for an extended period, please contact our support team.

Explanation: You may occasionally see 502: Bad Gateway or 504: Gateway Timeout. These both indicate that Zendesk's servers encountered an issue or were slow to respond while processing your request; like internal server errors, they originate on Zendesk's side and are outside of our control.

How to solve: Wait a moment and try again. These errors are typically temporary and resolve automatically. If either of them persists after multiple sync attempts, please contact our support team.

Explanation: You may occasionally see one of the following less common errors: 400: Bad Request, 405: Method Not Supported, 406: Not Acceptable, or 415: Unsupported Media Type. These indicate that something about the request sent to Zendesk was invalid, incorrectly formatted, or could not be returned in the expected format; 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.

Explanation: You may occasionally see 301: Moved Permanently or 304: Not Modified. These indicate that the Zendesk resource has been moved to a new location, or that it has not changed since your last request, so no new data was returned. Neither is an error as such, and both are typically handled automatically.

How to solve: No action is usually required; your widget will continue retrieving data at the next scheduled sync. If a widget consistently returns no new data, please contact our support team, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your Zendesk 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.