Understanding BigCommerce Errors in Hurree

If you're experiencing issues with your BigCommerce widgets, this guide explains the most common errors and how to resolve them.

If you encounter an error that isn't covered below, please get in touch with our support team for assistance.

Explanation: The credentials used to connect your BigCommerce account are missing, incorrect, or no longer valid, preventing your widgets from retrieving updated data.

How to solve: Reconnect your BigCommerce account through Hurree using valid credentials for the account you want to report on. If the issue continues after reconnecting, please contact our support team for assistance.

Explanation: This message indicates that the request could not be completed because your BigCommerce account requires a payment update.

How to solve: Ask your store owner or billing administrator to review the store's billing status in BigCommerce and resolve any outstanding payment issue. Once resolved, try again. If billing is up to date and the message remains, please contact our support team.

Explanation: Your connection does not have the permissions needed for the requested BigCommerce resource. This can happen when the API account or app lacks the required access scopes, or the request references the wrong store.

How to solve: Ask your BigCommerce administrator to check that the API account or app used by Hurree has the required access to the data you're reporting on. Confirm that you connected the correct store, then refresh the connection once any access changes have been made. If the issue continues, please contact our support team.

Explanation: The requested BigCommerce resource does not exist at the reference used by the widget. An order, product, customer, or other record may have been deleted, or the widget may refer to a different store.

How to solve: Check that the record exists in the BigCommerce store connected to Hurree. If it has been removed or the wrong store is selected, update your widget settings to use an available data source.

Explanation: BigCommerce rejected the request because it conflicts with an existing resource or a condition on that resource. The exact reason depends on the operation; it does not necessarily mean there is duplicate data.

How to solve: Review the relevant record in BigCommerce and try again. If the error continues on a reporting widget, please contact our support team with the message shown. Do not delete or change store records solely to clear the error.

Explanation: This message indicates that the BigCommerce resource referenced by the request has been permanently deleted and is no longer available through the connection.

How to solve: Update your widget settings to use an active record or data source. If you believe the resource should still be available, please contact our support team so we can check the reference.

Explanation: Too many API requests have been made within the permitted time window. Requests from other integrations using the same account may also contribute to the limit.

How to solve: Wait before trying again, or check your widget after the next scheduled sync period. Avoid repeatedly refreshing while the limit is active. If this happens frequently, please contact our support team so we can review your BigCommerce connector configuration.

Explanation: An unexpected error occurred while BigCommerce was processing the request. This is a server-side error rather than a problem with your login credentials.

How to solve: 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 request method used is not supported by the BigCommerce API for this action. This is not normally resolved by changing your subscription or reconnecting your account.

How to solve: Please contact our support team so we can review the request made by the connector. No changes to your store data are required.

Explanation: BigCommerce cannot process the request at present. This can occur while the store is in maintenance mode or being upgraded, or if it has been suspended due to an administrative or billing issue.

How to solve: Check that your store is accessible and ask your store administrator to review any maintenance, suspension, or billing notices. If the interruption is temporary, wait a few minutes and try again. If the store is active but your widget still fails, please contact our support team.

Explanation: The connection did not receive a response in time to complete the request. This may be a temporary delay in BigCommerce or an intermediary service.

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.

Explanation: These messages indicate an invalid request (400), an unsupported request method (405), an unmet condition (412), a request exceeding the permitted size (413), a requirement the server could not meet (417), or a missing required condition (428). Some relate to how the connector constructs the request, rather than anything you need to change in BigCommerce.

How to solve: Review your integration and widget settings for incorrect entries and try again. For 413, try a narrower date range or smaller reporting scope where available. If the error persists, please contact our support team with the exact message and code.

If you've completed the troubleshooting steps above and are still experiencing issues with your BigCommerce widgets, our support team is here to help.