Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM (Archived)

In D365 online Can we time out a system workflow for 30 days, will it create any problem?

(0) ShareShare
ReportReport
Posted on by 105

What are the drawbacks and precautions to be taken while using "time out" or "wait" in System Workflow Dynamics 365 online

*This post is locked for comments

  • Suggested answer
    Sreevalli Profile Picture
    Sreevalli 3,256 on at
    RE: In D365 online Can we time out a system workflow for 30 days, will it create any problem?

    Hi Sanghvi,

    It's not a good idea to keep many process threads in waiting.

    Most importantly, every time when you hit the trigger it will create a new process and it will be in wait until it met the condition. lets say you have trigger on date field and it will wait for 30days after the date passed, and the user changed date while the process in wait, it will create a new process thread again and now 2 are in waiting, will execute together when it met the condition.

    So, as Rawish suggested you can go for console, that should scheduled on daily basis based on your logic it should fetch the data and then do the job.

    alternatively, if you want to avoid system/server dependency. you can create a custom entity and a workflow(self parent and child) will fire on record create and you can add your custom workflow logic(same as above console) and then it will wait for 1day from the process execution time. by this there will be only job in wait and executes on daily basis.

  • Suggested answer
    Rawish Kumar Profile Picture
    Rawish Kumar 13,756 on at
    RE: In D365 online Can we time out a system workflow for 30 days, will it create any problem?

    Hi Bhavik,

    I would say avoid them if you can!

    I would say 30 days is quiet a big amount of time.  and also factor the number of records.

    Imagine in a month you have 10,000 records for each one the workflow triggers and gets into "waiting condition" . the  process jobs, they would be lying there in the background.

    Try to find an alternative way may be use a plugin instead or may be a console application that runs every to retrieve records and check the condition etc ect.

    here is another approach that i use very frequently : passion4dynamics.com/.../escape-from-waiting-condition-workflows-microsoft-dynamics-crm-2016

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,466 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans