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
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
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.
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
André Arnaud de Cal... 291,711 Super User 2024 Season 2
Martin Dráb 230,466 Most Valuable Professional
nmaenpaa 101,156