web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Workflow designer usin...
Microsoft Dynamics AX (Archived)

Workflow designer using LARGE amount of memory

(0) ShareShare
ReportReport
Posted on by DeadmanWNC 295

We have a dedicated server for designing our AX 2012 R2 workflows on.

Normally an AX32.exe client will consume 100-200k of memory, as soon as we start the workflow designer the memory increases to 500-600k.

We are currently designing a "large" workflow with around 200 elements and the memory usage for ax32.exe has grown to over 2gb.

With the designer open, not being used just open in AX (no other clients or other activity on the server) the memory usage of ax32.exe will fluctuate between 1.2g and 2.2gb.

The designer client has become VERY slow, property forms will close at random,

Is this normal?

We have rebooted server and the memory usage returns to 100-200 k until the designer is opened, back up to 500-600 then we open the large workflow and again back to 2.2GB.

Would be good to get other peoples views on this...

The server is virtual with a quad core 2.8Ghz and 4-8gb of dynamic memory.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Yes it seems to be a standard issue, when you look at the processing the workflow wizard is doing in the background it's huge. I had the same issue where the workflows would either crash or just slow the whole computer down while building. 

    I got round it by creating an RDP connection to AX with a dedicated server, nobody else but me had access to it. It partially solved the issue but when it gets over a certain amount of elements it still struggles. 

    We actually split the workflow down into smaller subworkflow chunks to take the burden off the 'Master' directing workflow. Rather than having 150 elements we have 10 workflows with 15 elements (example numbers).

    Hopefully this helps.

  • Suggested answer
    guk1964 Profile Picture
    guk1964 10,888 on at

    Its also important to minimize the load. The workflow batch runs across all companies, not just the one in which you are transacting,  which is another reason not to have test demo or training companies in the production instance.

    Cleaning up old messages is also essential housekeeping.

    Check the frequency of the workflow batch - the default setting of 1  min will not be enough for a 200 step workflow to complete before it times out..

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans