Understanding FreshBooks Errors in Hurree

If you're experiencing issues with your FreshBooks 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.

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

How to solve: Check that your FreshBooks 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 FreshBooks resource could not be found. This may occur if an invoice, client, expense, project, or other record has been deleted, or if the reference is incorrect.

How to solve: Review the relevant FreshBooks account 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 FreshBooks resource you're trying to access is being modified by another request, so it is temporarily unavailable to prevent conflicting changes.

How to solve: Wait a moment and try again; access is restored automatically once the other request finishes. If the conflict continues for an extended period, please contact our support team.

Explanation: FreshBooks 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 FreshBooks' servers. This is not caused by any action on your part, and as the issue originates within FreshBooks' 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: The action requested is not currently supported by FreshBooks' API.

How to solve: Please contact our support team if you believe this feature should be available, and we'll investigate.

Explanation: FreshBooks 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 FreshBooks. If the issue persists for an extended period, please contact our support team.

Explanation: Alongside standard error codes, FreshBooks returns its own numbered codes. These indicate that access has been denied (1003), write access has been denied for the resource (1038), or the account referenced is inactive (1042).

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

Explanation: The FreshBooks resource referenced in the request has been deleted (1011) or could not be found (1012).

How to solve: Review the relevant FreshBooks account and verify that the resource still exists. If it has been removed, update your widget settings to use a different record or data source.

Explanation: These indicate an issue with the dates used in the request, an invalid date range where the end date falls before the start date (1007), a missing date range (1008), a datetime or date format error (1016 and 1033), or a problem with a date filter (1023).

How to solve: Review the date range on your widget and confirm that the start date comes before the end date and that a complete range has been selected. If the error persists after adjusting your dates, please contact our support team.

Explanation: These indicate that the request attempted to group by a column that is already in use (1009) or is unknown (1010), or that a pagination value was invalid (1013 and 1014).

How to solve: Review your widget settings, particularly any grouping or breakdown options, and try again. These errors are usually handled automatically, so if one persists, please contact our support team.

Explanation: These indicate that a value in the request already exists in FreshBooks, for example, a duplicate tax (1019 and 1026) or another duplicate value that must be unique (1029).

How to solve: Review the relevant data in your FreshBooks account for duplicates and remove or amend them, then try again. If the issue persists, please contact our support team.

Explanation: A file could not be uploaded (1020), downloaded (1021), or deleted (1022) as part of the request.

How to solve: Wait a moment and try again. If the same file consistently fails, check that it is still available in your FreshBooks account, and please contact our support team if the issue persists.

Explanation: These indicate that something about the data in the request did not meet FreshBooks' requirements, for example, a missing required field, an invalid or out-of-range value, an unsupported character, or a number, percent, boolean, or filter value that was incorrectly formatted. They are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration and widget 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.

Explanation: These indicate that a system exception occurred within FreshBooks while processing the request, or that a specific attribute could not be set or updated. As they originate within FreshBooks, they are outside of our control.

How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If any of these errors persist, please contact our support team with the error name you're seeing, and we'll investigate.

Explanation: You may occasionally see 400: Bad Request or 405: Method Not Supported. These indicate that one or more elements of the request sent to FreshBooks were invalid or incorrectly formatted; 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 either of these errors persists, please contact our support team with the error name you're seeing, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your FreshBooks widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.