If you're experiencing issues with your Sage 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.
You do not have permission to access this resource
Explanation: You don't have permission to access this Sage 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 Sage.
How to solve: Check that your Sage 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.
The requested resource could not be found.
Explanation: The requested Sage 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 Sage 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.
The request timed out.
Explanation: The request took too long to complete, so Sage stopped waiting for a response. This can happen during periods of slow connectivity or heavy load.
How to solve: Check your connection and try again. If the timeout keeps recurring, please contact our support team so we can investigate.
This request conflicts with an existing resource.
Explanation: The request could not be completed because it conflicts with an existing resource in Sage, such as a duplicate record.
How to solve: Review the relevant data in your Sage account for duplicates or conflicting records and try again. If the issue persists, please contact our support team.
Sage could not process this request.
Explanation: The request was valid but could not be completed due to a business logic error in Sage, for example, data that doesn't meet Sage's accounting rules.
How to solve: Review the relevant data in your Sage account and try again. If the issue persists, please contact our support team.
This resource is temporarily locked.
Explanation: The Sage resource you're trying to access is currently being updated by another process, so it is temporarily locked to prevent conflicting changes.
How to solve: Wait a moment and try again; the lock is released automatically once the other process finishes. If the resource remains locked for an extended period, please contact our support team.
You've reached the Sage API limit (429)
Explanation: Sage 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 contact our support team so we can review your Connector configuration.
Sage internal server error (500)
Explanation: An unexpected error occurred on Sage's servers. This is not caused by any action on your part, and as the issue originates within Sage'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.
Sage gateway errors
Explanation: An error occurred with Sage's API gateway or content delivery network while processing the request. Like internal server errors, these originate on Sage's side and are outside of our control.
How to solve: Wait a moment and try again. Gateway errors are typically temporary and resolve automatically. If either error persists after multiple attempts, please contact our support team.
⚠️ Note: This article is intended only for Hurree users troubleshooting Sage Widget errors within the Hurree platform. If you're seeing Sage errors outside of Hurree, please visit Sage's Help Center.