Understanding Typeform Errors in Hurree

If you're experiencing issues with your Typeform 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 Typeform connection. This usually happens when your authorisation has expired, your password has been changed, or access to Hurree has been revoked from within your Typeform account.

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

Explanation: The data you're trying to access isn't available on your current Typeform plan. Some Typeform data is only available on higher-tier subscriptions.

How to solve: Review your subscription in Typeform to confirm which features are included on your plan, and upgrade if the data you need sits on a higher tier. Once your plan has been updated, refresh your connection in Hurree and try again.

Explanation: You don't have permission to access this Typeform 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 your Typeform workspace.

How to solve: Check that your Typeform 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 Typeform resource could not be found. This may occur if a form, response set, or workspace has been deleted, if it has been moved, or if the reference is incorrect.

How to solve: Review the relevant Typeform account and verify that the form or workspace 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 an existing item in Typeform. This typically happens when the same record is being updated in two places at once, or when a duplicate entry already exists.

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

Explanation: The Typeform resource you're trying to access has been permanently deleted and is no longer available. Unlike a 404, this confirms the item existed previously but cannot be recovered.

How to solve: Update your widget settings to point to an active form or workspace. If you believe the resource was deleted in error, check your Typeform account or contact your administrator.

Explanation: Typeform restricts the number of requests that can be made within a given time period. 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 Typeform widgets refreshing at the same time.

Explanation: An unexpected error occurred on Typeform's servers. This is not caused by any action on your part, and as the issue originates within Typeform'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: The action requested isn't currently supported by the Typeform API. This usually means the data or functionality you're looking for isn't available to external integrations.

How to solve: No action is required on your side. If you believe this feature should be available, please contact our support team, and we'll look into whether it can be supported.

Explanation: Typeform 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 Typeform is back online. If the outage appears to be prolonged, you can check Typeform's status page for updates.

Explanation: Typeform did not respond within the expected time frame. This is usually caused by a temporary delay or heavy load on their servers rather than a problem with your account.

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

Explanation: You may occasionally see 400: Bad Request, 405: Method Not Supported, 412: Precondition Failed, 413: Request Too Large, 417: Expectation Failed, or 428: Precondition Required. These indicate that something about the request sent to Typeform was invalid, incorrectly formatted, too large, 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 Typeform 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.