Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a workflow with a step to Timeout for 1 day (wait condition-> workflow -> timeout -> equals-> 1 day duration). The workflow is acknowledging that it should wait for a day , it's checks the step, and goes straight on to what I would like it to do after the timeout, except it didn't wait/timeout for a day!
I have a 6 waits/timouts in quick succession, not sure if this is causing it? For example, if X is true it should timeout for 3 days before taking the required action(s), if Y is true it should timeout for 2 days before taking the required action(s) otherwise it should timeout for 1 day and then take the particular action.
By "6 waits/timouts in quick succession" do you mean that the workflow is triggered 6 times? If so, please check the triggering criteria on the workflow, or any plugin on the workflow entity that could cause the workflow to be triggered multiple times.
Thank you for the reply. No, it doesn't trigger 6 times; it triggers on the outcome of a case type being updated, there are 6 outcomes but it only triggers once before checking which of the outcomes was selected. Each of these outcomes has a different email follow up email to be sent or other action which needs to be taken, but with a different time wait depending on the outcome. It's not waiting!
can you show us the wait condition, it may be incorrect? but explaining the logic of the wait condition it's impossible for us to say why it isn't waiting
For those who may be interested the situation appears that I have run into the maximum number of conditions that are allowed. I'm pretty sure I can resolve this by moving this logic into a child workflow. Wish me luck!
Thank you both for your help.
Business Applications communities