Understanding Ace360 Errors in Hurree

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 Ace360 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 Ace360 plan does not support the feature or data you're trying to access. Some Ace360 data is only available on higher-tier subscriptions.

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

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

How to solve: Check that your Ace360 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 Ace360 resource could not be found. This may occur if a record has been deleted, or if the reference is incorrect.

How to solve: Review the relevant Ace360 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 Ace360 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 Ace360 data, update your widget settings to use a different record or data source within your account.

Explanation: Some of the data provided with this request failed validation, meaning Ace360 could not process 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: Ace360 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 Ace360's servers. This is not caused by any action on your part, and as the issue originates within Ace360'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: Ace360 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 Ace360. If the issue persists for an extended period, please contact our support team.

Explanation: You may occasionally see one of the following less common errors: 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 Ace360 was invalid, incorrectly formatted, or could not be processed, 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.