Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 | Upcoming TechTalks
Hi CRM Community ,
We have a OOB workflow which will wait and rerun after 10 minutes.
Recently we observed the workflow had waited more than 10 minutes (infrequently - twice in 2 months period).
The Below Error was logged at the time when the workflow waited for more than 10 minutes in the Event Viewer.
"The category specified (*******) does not exist .
(Reporting Process : Microsoft.CRM.Sandbox.WorkerProcess , AppDomain:C:\Program Files\Microsoft Dynamics CRM\Server\Bin)"
Source : MSCRMTracing
Event ID : 17155
I would like to request any insights or technical help on this issue .
It would be great help if you provide the workflow you written on that (ScreenShot).
Use timeout instead of wait
Here is some of the waiting workflow might it would be helpful
If answer is helpful to you Please mark as Verified
Thanks for the response.
We are Currently using Timeout for our workflow. In the current screenshot below the workflow is waiting more than 10 minutes before Updating the case in Step one .
When you say more than 10 minutes, does it execute in 11 or 12 minutes? Or just throws an error as you mentioned and doesn't execute at all?
It does not throw any error in the workflow. It waits for 18 minutes or more than that and completes the update step. Whenever it waits for more than 10 minutes the below Error was logged in the Event Viewer.
Business Applications communities