Skip to main content
Understanding Xero Errors
Niamh McGlade avatar
Written by Niamh McGlade
Updated over a week ago

Below you will find an explanation for errors you may encounter on your Xero widgets. These errors are uncommon and if you see an error that is not detailed below please get in touch with a member of our team.

Invalid authorisation credentials.

Explanation: The Authentication process needed to connect your Xero account to Hurree failed because the information provided to verify your identity is invalid.

This means that your login details, such as username, password or token are incorrect, missing or not in the expected format. This could be due to a mistyped or forgotten password, an expired or revoked token, or an incorrect username.

How to solve: If you encounter this error you should double-check your authentication information to ensure it is correct. We recommend reverifying your username, password and any other required credentials. In some situations, you may need to reset your password. If the issue persists please contact your account admin.

You do not have permission to access this resource.

Explanation: This error indicates that you do not have the necessary permissions to access the resource you have requested.

How to solve: To resolve this issue you will need to contact the admin of the Xero account and ask them to update your permissions.

The resource you have specified cannot be found.

Explanation: Unfortunately the resource you are trying to access using Hurree can not be found. This may be a result of something being deleted or removed from your account.

How to solve: If you see this error we recommend checking the associated Xero account to ensure that the resource you are trying to receive data from hasn’t since been deleted or archived.

Something went wrong on Xero’s end

Explanation: In some instances, a third-party tool will experience issues within its own system which is out of our control.

How to solve: These outages usually don’t last long so we recommend waiting a short time and then trying again. If you are experiencing this error for a prolonged period of time please get in touch with our support team.

Did this answer your question?