Custom Messaging APIs might not be the most suitable category, but I just haven't found a better option. We have performance problems with Dataverse plugins in general, so it doesn't fit into any category.

Some of our plugins fail with such an error (Operation not allowed as plugin execution exceeded maximum allowed time), which makes us think that there is some undocumented limitation about how many times/how frequently can a certain plugin be executed. It is definitely NOT the 2-minute execution timeout limit (System.TimeoutException: Couldn’t complete execution of the xxxx plug-in within the 2-minute limit), which we are well aware of.

Our plugin does nothing time-consuming, plugintracelog.performanceexecutionduration constantly stays below 100 msecs. We haven't experienced it in most environments, but have a single customer who is running a contact centre with ~700 agents and several thousand phone calls get created each day. We have a few plugins hooked up for - amongst others - the create message of phonecall and connection entities, this is where (so far) this problem came up.

As a workaround, we ported the affected plugins to a CodeActivity with no other code changes and added to a synchronous workflow, triggered on the same event. There is no error anymore, so the problem is definitely not in the code (these are rather simple plugins).

This problem came up during the daily operation of this high-volume customer, but we could reproduce it when migrating large amount of data, with the plugins enabled.

I had a conversation with support, they suggested to submit the problem here.

So there should either be

• a clear documentation on performance limitations of plugins, and/or
• these limitations should be revised because are causing problems in case of high-volume scenarios.

We do understand that there has to be a limit on how many times a plugin can be executed, but it should be somehow tied to the number of user licenses, to avoid problems in high-volume environments.