Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
AX2009 Workflow performance / Issue
MyoSandar
Member Posts: 2
in Dynamics AX
Hi All,
My client is facing a serious workflow performance issue and have a lot of records end up with Error(stop). The workflow tables are very huge and have a lot of records in MessageQueueTable (few millions). It takes around 1 hour to assign to the approval or change the status (we schedule the batch job every 1 min).
We already separated the dedicated server for workflow with very high spec.
I would like to check if there any way to scale the workflow server? I have found a resource page for the workflow but it doesn't mention anything regarding with load balancing or cleaning up the history workflow.
Have you encountered the same issue before? How do you resolve it? As I am app consultant with little knowledge in technical, I would like to have some idea which I can talk to my technical team.
thanks for your time.
Regards,
Yuan
My client is facing a serious workflow performance issue and have a lot of records end up with Error(stop). The workflow tables are very huge and have a lot of records in MessageQueueTable (few millions). It takes around 1 hour to assign to the approval or change the status (we schedule the batch job every 1 min).
We already separated the dedicated server for workflow with very high spec.
I would like to check if there any way to scale the workflow server? I have found a resource page for the workflow but it doesn't mention anything regarding with load balancing or cleaning up the history workflow.
Have you encountered the same issue before? How do you resolve it? As I am app consultant with little knowledge in technical, I would like to have some idea which I can talk to my technical team.
thanks for your time.
Regards,
Yuan
0