web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

timeout in plugins

(0) ShareShare
ReportReport
Posted on by 70

Can we extend plugin's timeout to 5 mins in online CRM instance .

if yes, then how ?

I have the same question (0)
  • Suggested answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello,

    It's not possible. I would recommend to consider WebHooks to AzureFunction as alternative to plugins. You will not have those 2 mins timeout issues there.

  • Benedikt Bergmann Profile Picture
    190 on at

    Hej,

    if it is a async Plugin you could also create a Power Automate Flow instead. They do have a timeout of 10 min, if i remember correctly.

    //Benedikt

  • Suggested answer
    thonda Profile Picture
    on at

    Sandbox plugin execution timeout is only 2 mins for good. Recommended splitting the functionality into multiple plugins that pass data among themselves using the shared variables property of IPluginExecutionContext. Though SharedVariables usage is always described for plugin steps of different stages, I believe you should be able to share data using them between plugin steps of the same stage. I find the limitations of SharedVariables given in this blog is a good read to grasp a clear understanding of them. One other common model some customers achieve this is by parent-child background workflows with custom activity step, this kind of pattern is more suited when you do not know exactly how long the functionality execution takes place. Here are some recursion patterns described https://us.hitachi-solutions.com/knowledge-center/recursive-workflows-dynamics-365-customer-engagement/ ,  https://www.powerobjects.com/blog/2012/11/09/create-recursive-or-scheduled-workflows-in-crm/ , you may need to improvise on the concepts given in these blogs to achieve your requirement. Also please be aware of the fact that there is a hard limit about the number of times recursion can occur in workflow execution.

    The workflows you create include logic to detect and stop infinite loops. If a workflow process is run more than a certain number of times on a specific record in a short period of time, the process fails with the following error: This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. The limit of times is 16.

    The above are more classic(legacy) of handling the requirement, As another commentator mentioned Power Automate is a more futuristic way of designing for the above requirement. 

    Regards,

    Praveen T

    D365 Support Engineer

    Microsoft Corporation

  • Suggested answer
    RajuB Profile Picture
    on at

    Also as said above. here is the documentation on the usage and limitation.

    docs.microsoft.com/.../avoid-batch-requests-plugin

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 45 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 27 Most Valuable Professional

#3
Soundari Profile Picture

Soundari 15

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans