PL 400 : implement API limit retry policies (Use platform APIs)

API limits act as guardian to control random and unpredictable surges in API request volume. A large number of requests create availability problems and reduce performance, in other words, API limits ensure the health and accessibility of the API. With HTTP API requests, this error usually appears as a response with a 429 status code. It also sends additional information to indicate the time required to wait until another request is attempted. This header is usually called "Retry-After".


Dataverse API limits help ensure service level, availability, and quality. Dataverse API limits are part of the Power Platform request limit and allocation. There are two categories of limits that apply for Dataverse.

  • Entitlement limits
  • Service Protection limits
Entitlement limits:

Entitlement limits are associated with type of license assigned to each user. If user exceeds their requests, the administrator would be notified.

Service Protection limits:

To maintain the performance and availability, Microsoft applies some limits on Dataverse API usages. Such limitations only effect to large number of API requests to prevent to surge the unexpected and random requests. The limit also apply on concurrent connection per user account, the number of API request per connection, and the amount of execution time. When one of these limits is exceeded an exception will be thrown by the platform.

Service protection limits apply to all external web service requests.

Microsoft always recommends to apply patterns to retry operations after a period of time when these exception are returned. These limits are designed to detect when client applications are making extraordinary demands on server resources.

The limit doesn't effect the normal users of interactive clients.

Plug-ins and custom workflow activities implement business logic triggered by incoming requests. Service security limits do not apply to plug-ins and custom workflow activities. Plug-ins and custom workflow activities are uploaded and run within an isolated sandbox service. Dataverse operations implemented on a sandbox service do not use a public API endpoint.

Retry Operation:

When a Service protection  API limit error occurs, it will provide a value indicating the length of time before any new requests from the user are processed.
  • When a 429 error is returned from the Web API, the response will include a Retry-After with number of seconds.
  • With OrganizationService, a TimeSpan value is returned in the OrganizationServiceFault.ErrorDetails collection with the key Retry-After.
In an interactive application re-try, the developer should display a message that the server is busy while the user retry the request made by the user and try again in a non-interactive application re-try, leaving the client application to simply wait before the period elapses. Must practice is sending request again.

The service protection API limits are evaluated per user.

Service protection API limits are enforced based on three facets:
  • The number of requests sent by a user.
  • The combined execution time required to process requests sent by a user.
  • The number of concurrent requests sent by a user.


The availability of servers depends on multiple factors, but each web server of environment will enforce these limits independently. As known, most environment will have more than one web server. Trial environments are allocated only a single web server.

The Retry-After duration will depend on the nature of the operations that have been sent in the preceding 5 minute period.

Conclusion:

The API limit does not impose any restrictions in use, obviously, it helps to increase performance and availability for all. Sometimes, developers write code without reading the documentation or unintentionally misuse the resource consumption, such limit prevents such incidents. Microsoft provides unlimited resources for commercial use, but also implements mechanisms that help use the Dataverse API in customizable ways.

Comments

Post a Comment

Popular posts from this blog

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more