CRM Crate

Understanding the 2 Minute Plug-in Timeout in Model-Driven Apps

In this blogpost, we will learn & understand the 2 Minute Plug-in Timeout in Model-Driven Apps/Dynamics 365. Before we begin, please ensure that you subscribe to CRM Crate so that you can stay updated in the field of Power Platform.

Understanding the 2-Minute Plug-in Timeout in Model-Driven Apps/Dynamics 365

A plug-in serves as a personalized event handler triggered by a particular event occurring during the processing of a Microsoft Dataverse data operation. It’s created as a custom class compiled into a .NET Framework assembly, which can then be uploaded and registered within Dataverse. You can register one or more compiled plug-in classes from an assembly onto specific events (known as steps) within the Dataverse event framework. Whenever the designated event happens during data processing, the code within the registered plug-in class kicks in, allowing you to enhance or adjust the default data processing behavior of the platform.

What is a Plug-in Timeout in Model-Driven App?

When working with Model Driven Apps / Dynamics 365 Customer Engagement, developers frequently come across a rather frustrating obstacle: the 2-minute plug-in timeout. This restriction can be frustrating, especially when dealing with complex processes or large datasets. However, we will understand the rationale behind this limitation can shed light on why it exists and how to work around it effectively.

Understanding the 2 Minute Plug-in Timeout in Model-Driven Apps

The 2-minute timeout is the maximum amount of time a plug-in can run before the platform forcefully ends its execution & cancels the database transaction. If a plug-in goes beyond this limit, it gets terminated, which could result in incomplete processes or partially processed data.

What are the reasons for 2-minute Plug-in timeout?

Below are the potential reasons for cancelling plug-in operation after 2-minutes:

  1. Improving User Experience: From the viewpoint of application users, long running operations & processes can cause annoyance and disappointment. Users anticipate responsiveness and prompt feedback from the application. By implementing a timeout, Microsoft ensures that user interactions stay seamless and uninterrupted, even when resource-heavy operations are ongoing in the background.
  2. Optimizing Performance: One of the main reasons for having a plug-in timeout is to optimize performance. Dynamics 365 / Model-Driven App operates in a shared multi-tenant environment, where multiple organizations utilize the same underlying infrastructure. To guarantee fair distribution of resources and prevent one organization’s processes from dominating system resources, Microsoft sets limitations like the 2-minute plug-in timeout.
  3. Preventing Infinite Loops: Plugins have the capability to trigger other plugins, which could lead to endless loops if not handled correctly. Implementing a time limit helps avoid such scenarios by stopping plugin execution if it runs for an excessive duration. Note: – You can handle looping issue with the Plugin “Depths”.
  4. Preventing Database Locking: Plugin executions have the potential to lock database records, affecting the system’s responsiveness and causing delays for other users requiring access to the same records. Implementing time limits helps mitigate these locking issues.
  5. Improving System Stability: If long-running processes were allowed to continue indefinitely, it could compromise the stability and performance of the Model-Driven App environment. By implementing a timeout, Microsoft can reduce the chances of resource depletion, system crashes, or slowdowns caused by poorly optimized plug-ins or infinite loops.

What are the workarounds for Plug-in timeouts?

Although the 2-minute plug-in timeout poses a challenge, developers can utilize a variety of strategies to effectively navigate this limitation:

  1. Introduce Asynchronous Execution: Whenever feasible, convert time-consuming operations to asynchronous processes. Utilizing Azure Functions enables operations to run independently of the triggering event, thereby lowering the likelihood of exceeding the timeout threshold. You can used a HTTP based Azure Function and invoke it from a Plug-in for handling long running operations. You can also use schedule jobs for carrying out your operations.
  2. Batch Processing: Divide down big tasks into smaller, more manageable portions. Employ batch processing methods to handle data gradually within the 2-minute timeframe. This not only respects the timeout restriction but also enhances scalability and dependability.
  3. Develop a Better & Optimized Code: Develop code efficiently to reduce execution time. Pinpoint and remove bottlenecks like redundant loops or resource-heavy operations. Incorporate best practices and design patterns to streamline code execution.

While the 2-minute plug-in timeout in Model Driven Apps / Dynamics 365 may initially seem restrictive and annoying, it serves crucial purposes in maintaining system stability, performance, and user satisfaction. By understanding the reasons behind this limitation and employing effective mitigation strategies, developers can navigate this constraint effectively while delivering robust and efficient solutions within the Dynamics 365 ecosystem.

5 1 vote
Article Rating
Notify of
Inline Feedbacks
View all comments
error: CRM Crate Security Engine - Disabled Right Click & Selection!


Well Done,
Welcome to CRM Crate

Stay tuned with us and get all latest updates and learning in Microsoft CRM and related techonologes.