Priority-based throttling is a new feature in Microsoft Dynamics 365 Finance and Operations. It allows prioritization of OData and custom service-based integrations, to better align it with your needs.
As the volume of calls made increase beyond what endpoints can handle, the amount of service requests being sent to the system by both OData and Custom webservice begin to affect the reliability of the system. This is because the resources that run endpoints and the rest of the system are shared. As a result, the system will begin to throttle requests to ensure that Dynamics 365 Unified Operations users do not experience any degradation. Throttling will be enabled automatically for OData endpoints, Custom web service, DMF Rest API endpoints, and recurring integration dequeue and enqueue API. This is the case even if you haven't set any priorities.
Using Priority-based throttling
With priority-based throttling feature in Microsoft Dynamics 365, an administrator can align priorities through a number of ways:
Throttling based on priority allows the administrator to sort integrations into three categories: high, medium, and low. The administrator has to determine the criticality of the integrations and assign priority to make use of this functionality. The administrator can log in to D365 F&O to enable the throttling priority mapping filter and assign the appropriate priority level to a new integration account.
Found this blog useful? Read more here:
About UNIFY Dots