Understanding Asana Errors in Hurree

If you're experiencing issues with your Asana 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 not covered below, please contact our support team for assistance.

Explanation: This happens when the credentials used to connect your account are missing, expired, or no longer valid, preventing your Widgets from retrieving updated data.

How to solve: Reconnect your Asana 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 get in touch with our support team for assistance.

Explanation: Your Asana plan does not support the feature or data you're trying to access. Some Asana data is only available on higher-tier subscriptions.

How to solve: Review your subscription in Asana and upgrade if needed, or contact your Asana administrator to confirm which features are included in your current plan.

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

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

Explanation: The requested Asana resource could not be found. This may occur if a task, project, portfolio, or other resource has been deleted or moved, or if the reference is incorrect.

How to solve: Review the relevant Asana workspace 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 Asana resource you're trying to access has been permanently deleted and is no longer available.

How to solve: Deleted resources cannot be restored through the connection. To continue reporting on Asana data, update your Widget settings to use a different resource within your workspace.

Explanation: Asana limits the number of requests allowed within a given time window, and if your connected Widgets pull 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 get in touch with our support team so we can review your Connector configuration.

Explanation: Asana has blocked this request for legal reasons, for example, restrictions that apply to certain regions or content.

How to solve: Please contact our support team for further assistance, and we'll help you understand why the request was blocked.

Explanation: An unexpected error occurred on Asana's servers. This is not caused by any action on your part, and as the issue originates within Asana'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: Asana 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 Asana. If the issue persists for an extended period, please contact our support team.

Explanation: You may occasionally see 400: Bad Request. This indicates that one or more elements of the request sent to Asana were invalid or incorrectly formatted, it is typically handled automatically and is rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If the error persists, please contact our support team, and we'll investigate.