If you're experiencing issues with your Microsoft Dynamics 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.
Your Microsoft Dynamics connection could not be verified
Explanation: The credentials used to connect your Microsoft Dynamics account are missing or no longer valid. This usually happens when your authorisation has expired, your password has been changed, or access to Hurree has been revoked from within your Microsoft account.
How to solve: Reconnect your Microsoft Dynamics account through Hurree to restore access. Once reconnected, your widgets will begin updating again from the next scheduled sync.
There's an issue with your Microsoft billing details
Explanation: Your Microsoft Dynamics account requires a valid payment method before this request can be completed. Microsoft restricts access when a subscription has outstanding billing issues or has lapsed.
How to solve: Update your billing details in your Microsoft account settings and confirm your Dynamics subscription is active, then try again. If the error persists once your billing is up to date, please contact our support team.
You do not have permission to access this resource
Explanation: Your account does not have the permissions required to access this Microsoft Dynamics resource. This can occur if your security role has changed, access has been revoked, or you have not been granted the appropriate level of access within your Dynamics environment.
How to solve: Review your Microsoft Dynamics account permissions, or contact your account administrator and ask them to review your security role. 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 Microsoft Dynamics resource could not be located. This may occur if an account, contact, lead, opportunity, or other record has been deleted or moved within Microsoft Dynamics, or if the reference is incorrect.
How to solve: Review the relevant Microsoft Dynamics environment and verify that the record or data source still exists, then try again. 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 and was cancelled. This is usually caused by a temporary delay on Microsoft's side, or by a particularly large volume of data being requested at once.
How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If timeouts continue, consider narrowing the date range on your widget to reduce the amount of data being retrieved.
This request conflicts with an existing item
Explanation: The request could not be completed because it conflicts with an existing item in your Microsoft Dynamics account. This typically happens when the same record is being updated in two places at once, or when a duplicate entry already exists.
How to solve: Review your Microsoft Dynamics data for duplicate or conflicting entries, then try again. If the conflict continues, please contact our support team for assistance.
This resource has been permanently deleted
Explanation: The requested Microsoft Dynamics resource has been permanently deleted and is no longer accessible. Unlike a 404, this confirms the item existed previously but cannot be recovered.
How to solve: Remove any references to the deleted record from your widget settings and point them to an active data source instead. If you believe the record was deleted in error, check your Microsoft Dynamics environment or contact your administrator.
An unexpected response was returned
Explanation: Microsoft Dynamics returned a response that Hurree did not recognise. This is uncommon and is not caused by any action on your part.
How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists, please contact our support team, and we'll investigate.
You've reached the Microsoft Dynamics API limit
Explanation: Your account has reached the maximum number of requests permitted within a given period. Microsoft Dynamics enforces request limits per environment, so this is most often triggered when a large volume of data is requested at once.
How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you see this error frequently, consider reducing the number of Microsoft Dynamics widgets refreshing at the same time.
Microsoft Dynamics is temporarily unavailable
Explanation: Microsoft Dynamics is currently unavailable, most often due to maintenance or an unexpected outage on their side. This is typically a transient issue.
How to solve: Wait a few minutes and try again. Your widgets will update automatically once Microsoft Dynamics is back online. If the outage appears to be prolonged, you can check the Microsoft 365 service health dashboard for updates.
Other Server Errors
Explanation: You may occasionally see 502: Bad Gateway or 504: Gateway Timeout. These both indicate that Microsoft's servers returned an invalid response or did not respond in time while processing your request; they originate on Microsoft's side and are outside of our control.
How to solve: Wait a moment and try again. These errors are typically temporary and resolve automatically. If either of them persists after multiple sync attempts, please contact our support team.
Other Request Errors
Explanation: You may occasionally see 400: Bad Request, 405: Request Method Not Supported, 412: Precondition Failed, 413: Request Too Large, or 415: Unsupported Media Type. These indicate that something about the request sent to Microsoft Dynamics was invalid, incorrectly formatted, too large, or in a format Microsoft Dynamics doesn't support; 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 you see 413 specifically, try narrowing the date range or scope of your widget to reduce the volume of data being requested. If any of these errors persist, please contact our support team with the error name you're seeing, and we'll investigate.
Need Additional Support?
If you've completed the troubleshooting steps above and are still experiencing issues with your Microsoft Dynamics 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.
⚠️ Note: This article is intended only for Hurree users troubleshooting Microsoft Dynamics 365 Widgets errors within the Hurree platform. If you're seeing Microsoft Dynamics 365 errors outside of Hurree, please visit Microsoft Dynamics 365's Help Center.