Workflow execution issues

(0) Share

Report

Posted on by Manmohan Mehta

1,185

We are using ax 2012 R3 and facing some issues with workflow. We observed that sometimes workflow stuck in pending state or for some even workitem doesn't get created for hours. We tried running workflow tutorial to explicitly run the workflow queue but its also time taking and not fruitful .

These workflow works fine generally however gets stuck abruptly and hence we are not able to debug the root cause.

Please suggest how we can debug these issue and fix them. Thanks

PS: Our environment is full complied, CIL and synch without any error.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Yasir Shahzad 1,635 on at

Like (0)

Report
Copy link

Link copied!

Dear Mehta....will you plz confirm the dates submitter and users ...infect try to make sure that dates and time is accurate...also tell me the workflows are customized or bydefault

Regards

Was this reply helpful? Yes No
Manmohan Mehta 1,185 on at

Like (0)

Report
Copy link

Link copied!

Hi Yasir, workflows we are having issues with are customized as well as out of the box.

I ensure that date & time are correct.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,667 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Manmohan,

I have seen serious delays at a customer. When the workflow configuration is too complex, it will take a lot of time to load during the workflow message execution batch. Also wrong customizations with e.g. a wrong index choice can cause delays. During these delays, the message queue will be longer and longer. E.g. at the customer, the time to execute one batch took over 2 hours. Then we did setup additional batch jobs to divide the load. It is still not super, due to some complex workflows, but quite acceptable. Except for month end closing...

You have to start monitoring if workflow batch jobs will end in errors. If so, it can hold some, but also a large number of messages for days. This because it assumes that after 10 minutes an executing batch job can be re-executed. If it fails again, the list with not processed messages can become longer and longer. If the batch job runs OK for 9 minutes and every 10th minute it fails, you have to find out which message causes the error.

If there are no errors, you have to monitor how many minutes the batches are taking every single run. Then you could try to find some performance issues related to e.g. missing or fragmented indexes.

Was this reply helpful? Yes No
Manmohan Mehta 1,185 on at

Like (0)

Report
Copy link

Link copied!

Thanks For reply Andre.

As per your suggestion, I looked into the batch job history and found there are some continuous errors coming from workflow (ref attached) batch however this is also not the one we are getting every time.

As I asked before please help me understand :

1. How can I split the load of workflow batch ?

2. How can I check the total number of workflows in a queue and remove any which is creating a trouble ?

3. To have more responsive workflow we have set the execution 1 per minute (I think which should be at least 5 pm ), Is this setup fine?

Thanks for your time...

Was this reply helpful? Yes No