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
Hi,Dynamics CRM 2016 8.2 on premise:
Even though the organization performs quite quickly, when I'm editing a workflow in my development environment, adding a step or popping up its properties can take 20 to 30 seconds most of the time.
Sometimes it's as fast as lightning, but usually changing the Stop workflow step from "success" to "failed" easily takes 15 seconds or longer.
During that time I see my IIS Worker Process (w3wp service) CPU usage rise up to 60-80% and as soon as the action is done, it reverts back to well, almost nothing.Any thoughts on this?Thanks!Jeroen
I would recommend you to see the overall performance analysis at system level rather than Workflow edit, also would recommend to clear browse cache from beginning then monitor the same.
If issue exists, you need to see the DB size , performance recommendations from clearing successful job tasks, number of records in POA table in DB
Check below URL also
I completely agree on your comments looking at it from a higher perspective, but the challenge is that the system performs flawlessly on any transaction I've been testing so far.
Only when editing a workflow it usually doesn't. "Usually" because every now and then it speeds up to a very workable max, for no longer than half an hour.
Well, I'll just start back at the drawing board to walk through the usual performance tweakers.
Maybe, just maybe this might ring a bell for someone.I have two workflows that I'm editing. Workflow A is an old one, used, published and edited quite a few times. Workflow B is a brand new one, hasn't even been published yet.If I add a (for example) conditional step, in the editing window of Workflow A, it takes about 25 seconds. In B it takes less than half a second. Both on the same organization.Still the application server CPU goes berzerk when adding the step on A, almost nothing happens on B.Any idea what may cause such a difference?
did you get anywhere with this?
We are having a major slowdown whilst editing a rather complex workflow and are being told thats just the way it is. im curious if others have had performance issue with the editor and if they resolved them.
I did get anywhere, but not there where I wanted to be.
I figured out that editing a realtime workflow is extremely slow, but editing async workflows isn't. So if I need to edit a realtime flow, I convert it to asynchronous, edit it and convert back to realtime.
Unfortunately no real solution but (for me) an almost acceptable workaround.
Business Applications communities