Power Platform Community Forum Thread Details

Plugin Instances Not Cached Anymore - New Instance Each Execution (Contradicts MS Docs)

Hi everyone,

I've discovered that Dataverse plugin instances are being created new for each execution, which directly contradicts Microsoft's official documentation.

The Documentation Says:

According to Microsoft's article Develop IPlugin implementations as stateless:

"Because the platform caches plug-in class instances, the constructor isn't called for every invocation of plug-in execution."

My Test Proves Otherwise:

I created a simple test plugin with a GUID property initialized in the constructor:

public class TestPlugin : IPlugin
{
    private Guid ExecutionContextId { get; } = Guid.NewGuid();
    
    public void Execute(IServiceProvider serviceProvider)
    {
        var tracingService = (ITracingService)serviceProvider.GetService(typeof(ITracingService));
        tracingService.Trace($"ExecutionContextId: {ExecutionContextId}");
    }
}

Test Results:

Expected: Same GUID in trace logs (proving instance is cached and reused)

Actual: Different GUID every time (proving new instance each execution

Environment Details:

Environment Type: Developer

Platform: Dataverse Online

Plugin Registration: Sandbox mode, Synchronous

Tested: August 2025

Test Method: Triggered plugin multiple times via entity update

Why This Matters:

This fundamentally changes how we should design plugins. The documentation strongly emphasizes stateless design because of instance caching, but if instances aren't cached anymore, this guidance needs updating.