Understanding Twilio Errors in Hurree

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

​How to solve: Reconnect your Twilio 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: The request could not be authenticated, or the connected account does not have permission to access the requested resource. This can occur if your permissions have changed or the connection was set up without all the required access.

​How to solve: Reconnect your Twilio account via Hurree and ensure all requested permissions are approved during setup. If the error continues after reconnecting with full permissions, please contact our support team.

Explanation: The requested resource could not be located. It may have been deleted or moved within Twilio, or the reference may be incorrect.

​How to solve: Verify the resource still exists in your Twilio account and try again. If it has been removed, you may need to update your Widget settings or select an alternative data source.

Explanation: The requested resource has been permanently deleted and is no longer accessible.

​How to solve: Deleted resources cannot be restored through the connection. Remove any references to it from your report settings, and update your Widget to use a different resource within your Twilio account.

Explanation: An unexpected error occurred on Twilio's servers. This is not caused by any action on your part, and as the issue originates within Twilio'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: Twilio's service is currently unavailable. This is typically a transient issue on their platform.

​How to solve: Wait a few minutes before trying again. Temporary outages are usually resolved automatically by Twilio. If the issue persists for an extended period, please contact our support team.

Explanation: You may occasionally see 400: Bad Request. This indicates that one or more elements of the request sent to Twilio were invalid or incorrectly formatted; it is typically handled automatically and is rarely caused by anything on your side.

​How to solve: Review your integration settings for any incorrect entries and try again. If the error persists, please contact our support team, and we'll investigate.