CRM 2016 Async plugins firing inconsisentely

(0) Share

Report

Posted on by Community Member

I have an entity with 4 plugins registered on the update message.

Two of the plugins are registered on the pre-operation pipeline stage and two of the plugins are registered asynchronously on the post-operation pipeline stage. All four plugins have different filtering attributes.

Each of the plugins serializes its context to an xml file as soon as the Execute method is entered. This is functionality baked into a base class we have and I have no reason to believe this would fail.

When testing the same record for an update I get inconsistent results.

Sometimes only the pre-operation pipeline plugins fire and sometimes all four plugins fire.

What is odd, is that I can tell by the value of the record I'm testing on, that all four plugins have fired. However in many cases the serialized context file isn't generated

I've experimented with changing both of the async plugins to synchronous and that seems to temporarily fix the issue. I've also experimented with disabling the pre-op plugins and only letting the async fire.

Has anyone dealt with a similar issue?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Drew Poggemann 4 on at

Like (0)

Report

Did you try restarting the Async service to see if resolves? Do you have multiple and one was restarted and the other wasn't?

Hope this helps

Thanks,

Was this reply helpful? Yes No
Suggested answer

Zohaib Uddin Khan 2,822 on at

Like (0)

Report

Seems like Asynchronous Service has some problem. Asynchronous Service is either installed on your CRM Web server or separate server.

Stop and Re-start the Asynchronous Service.

1.Go to CRM Web server.

2.Navigate to Start, select Administrative Tools, then click Services.

3.Go through the list and find Microsoft Dynamics CRM Asynchronous Processing Service. If you're unable to find on the CRM Web Server, then check your topology diagram and verify on every server in your topology.

4.Right-click Microsoft Dynamics CRM Asynchronous Processing Service in the Name column of the service listing.

5.Click Start or Stop. Or, you can click Properties in the shortcut menu and then click Start or Stop in the dialog box.

You must have System Administrator privileges to stop or start the service.

Apart from this try Plugin Profiler to check the behaviour.

Was this reply helpful? Yes No
Suggested answer

ScottDurow 21 on at

Like (1)

Report

Hi - this is expected behaviour for async plugins since the execution order is not guaranteed to be the same as when the event fired. This is due to the parallel nature of the async servers.

Sync plugins will however always fire in the same sequence they are triggered.

Hope this helps

Was this reply helpful? Yes No
Suggested answer

Dynamics_Alok 1,746 on at

Like (0)

Report

Execution Order of Async Plugin does not work on any statistical way.It depends on many factors like free System Resources ,AppDomain and many others including CRM services and records.

Was this reply helpful? Yes No