diff --git a/powerapps-docs/developer/data-platform/analyze-performance.md b/powerapps-docs/developer/data-platform/analyze-performance.md index fda75ee8a8..7a28588224 100644 --- a/powerapps-docs/developer/data-platform/analyze-performance.md +++ b/powerapps-docs/developer/data-platform/analyze-performance.md @@ -18,7 +18,7 @@ When you add business logic to your plug-in you should be aware of the impact yo ## Time and resource constraints -There is a hard **2-minute time limit** for a Dataverse message operation to complete. This limit includes executing the intended message operation and all registered synchronous plug-ins. There are also limitations on the amount of CPU and memory resources that can be used by extensions. If the limits are exceeded an exception is thrown and the entire message operation will be cancelled (rolled back). +There is a hard **2-minute time limit** for a Dataverse message operation to complete. This limit includes executing the intended message operation and all registered synchronous and asynchronous plug-ins. There are also limitations on the amount of CPU and memory resources that can be used by extensions. If the limits are exceeded an exception is thrown and the entire message operation will be cancelled (rolled back). If the time limit is exceeded, an will be thrown. If any custom extension exceeds threshold CPU, memory, or handle limits or is otherwise unresponsive, that process will be killed by the platform. At that point any current extension in that process will fail with exceptions. However, the next time that the extension is executed it will run normally. @@ -27,7 +27,7 @@ If the time limit is exceeded, an will be thrown. > > Our general recommendation is to limit the time your plug-in takes to execute to no more than 2 seconds. > -> If your plug-in requires more time to execute, consider registering your plug-in for asynchronous rather than synchronous execution. In fact, asynchronous execution should always be considered first when possible as it results in better application responsiveness and system scalability. +> If your plug-in requires more time to execute, consider registering your plug-in for asynchronous rather than synchronous execution. In fact, asynchronous execution should always be considered first when possible as it results in better application responsiveness and system scalability. However, the asynchronous plug-in still has 2-minute time limit. More information: [Best practices and guidance regarding plug-in and workflow development](best-practices/business-logic/index.md)