How to best handle a plugin running more than 2 minutes.

(0) Share

Report

Posted on by Community Member

Hi everyone

We have a plugin that being fired on the creation of a systemuser which deletes and creates relationships. This process sometimes takes up to 8 minutes.

This is because we have a sync plugin on the associate message.

We see 3 possible solutions at the moment.

1. We change the plugin on the associate message to async. We tested this and the duration of the plugin goes down to 1 minute. If we want to do this as a final solution, we will have to analyze the consequences for the rest of the system.

2. We use an AzureFunction/Job to make the required changes and we follow the progress in a workflow.

3. We use a ServiceBus in azure and we follow the progress in a workflow.

We're looking to find the best solution.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Community Member on at

Like (1)

Report

RE: How to best handle a plugin running more than 2 minutes.

Hi

I did have a similar/related issue on one of the Plug ins and we use on CRM online .

In my case the issue I was getting is a 2 minute limit time out error so the Plug in failed to execute completely .

So whether its a plug in or custom workflow activity synchronously or asynchronously there is a 2minute limit imposed on the execution of a (message ) request .If the limit is excided a System. Timeout exception is thrown .

If it was on premise I could have updated the 2 minutes limit but in an unsupported way but my problem was we are online

1)I changed the plug in from synchronous to asynchronous but it still did not resolve my issue .

2)To Resolve this a windows service (or console app ) has been created on an Azure server that pulls the data from CRM Online/dynamics 365 applies its computation and executes the results back to CRM .The windows service is performing exactly the same function as the plug in(used that same logic).It runs on one of our web services server .I also had to disable the plug in

-Since then I have never had an issue and its even much faster than before .

I suggest you try option 1 but not so sure a workflow is a good idea performance wise .

Was this reply helpful? Yes No
Suggested answer

Mahendar Pal 45,095 on at

Like (0)

Report

RE: How to best handle a plugin running more than 2 minutes.

Hi,

I will suggest you to go through with Azure option if possible, because both syn and asyn have 2 min timeout limit so even though your logic is working in asyn at present but it may fail. Or if you still want to go with workflow make sure to test all possible scenario.

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: How to best handle a plugin running more than 2 minutes.

Which of the two azure options would you suggest?

1. an AzureFunction/Job

2. a ServiceBus in azure

Was this reply helpful? Yes No
Aparna1 222 on at

Like (0)

Report

RE: How to best handle a plugin running more than 2 minutes.

Hi Rodz,

Can you help me regarding how to create console app on Azure server. It would be great if can get an example. I am also facing an issue like this.

Thanks

Aparna

Was this reply helpful? Yes No
Aparna1 222 on at

Like (0)

Report

RE: How to best handle a plugin running more than 2 minutes.

Hi Rodz,

The solution seems quite good. But could you please let me know how can we trigger or run this console application on the creation and update of record as we do in case of plugins.

Thanks

Aparna

Was this reply helpful? Yes No
Suggested answer

Mahendar Pal 45,095 on at

Like (1)

Report

RE: How to best handle a plugin running more than 2 minutes.

Hi,

You can't call your exe on the online plugin,

For flow you can refer : http://himbap.com/blog/?p=3268 similarly you can configure update event on flow to update child records

For Azure, you can refer: docs.microsoft.com/.../gg334766(v=crm.7)

Was this reply helpful? Yes No