Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I'm wondering how long a workflow will stay in a Status Reason of "Waiting" before it times out/gets cancelled automatically?
I have a workflow for "Renewal" Opportunities with the following step: "Wait until Today's date >= 3 months before Renewal Date." Then, the record is updated. I'm worried that if the workflow has a status of "Waiting" for too long, it will cancel automatically. Will this be an issue? If yes, what is a better way to handle "Renewal Opportunities", so the Opportunity Name gets updated with the word "Renewal" 3 months before the date in the "Renewal Date" field?
Realistically, a workflow can wait as long as you want it to wait unless someone explicitly cancels it. To demonstrate it, I've made a workflow step wait until 2024 (this can be anything, as long as Dynamics is allowing you)
So, you'll not timeout in this scenario. If everything with the record or or workflow Process itself remains stable, it'll wait till whenever you want it to wait.
Hope this helps.
Waiting means that each records which satisfy workflow wait condition will create different instance with waiting status , and internally workflow async process execute those instance depending on workflow condition and do the success operation if its satisfy. As you know wait conditiin is only applicable for async workflow and there is no timeout for asynchronous workflow.
You can have look below scenario -
Business Applications communities