Answered

Workflow Stopped working

(0) Share

Report

Posted on by Community Member

Dear Experts,

Our worklfows been working fine since early `go live` and didn't had any issues. Last Thursday out of a sudden it stopped working in all environments. Problems we are having with Purchase Order/Requisitions workflows. While submitting for approval it stucks in status `` in review``. We have re-booted AX/AD servers and it didn't help. We haven't done any changes in worklfows. Any ideas what could possibly go wrong? Any suggestions are welcome

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Suggested answer

Prashant Singh 8,802 on at

Like
a
(0)

Report
Copy link

Link copied!

Dear Viz,

I will suggest please check the workflow batch Job.

1. Workflow Message Processing Batch Job is working or not?

2. Also check the workflow history if there is some error or something.

Regards,

Prashant Kumar

Was this reply helpful? Yes No
Mea_ 60,286 on at

Like
a
(0)

Report
Copy link

Link copied!

Did you check workflow batch job ?

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Prashant,

I just checked the batch job history and one of the jobs stuck on status ``executing`` last Thursday. I don't see any other error messages there.

Was this reply helpful? Yes No
Suggested answer

Mea_ 60,286 on at

Like
a
(0)

Report
Copy link

Link copied!

You need to go to SQL management studio select your DB and run "All blocking transactions" report. Probably there is dead lock in DB so you will have to kick this session

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like
a
(0)

Report
Copy link

Link copied!

Check the workflow history form to see whether the instance is in an error state. Maybe the approver does not have the appropriate access rights in AX

A common cause if that the default batch frequency is 1 min which is typically too short and there is a risk that a new work flow tries to start before the previous one completes as more users and more companies are introduced. Old uncompleted/abandoned works orders will also impact the batch process. Particularly if you have a test company in the production environment because the batch runs across all companies) So, if this is not already done set this to something more reasonable like 5 min. If you have many users and many processes then a dedicated aot for batches maybe worth while.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

Thank you for all your replies. One of the users that had workflow signed to it have been removed from Active Directory and we do believe this was one of the reasons why our workflow stopped working. To solve the problem we had to re-activate some of the inbound ports in system administration that are related to workflow/user session services and cancel all ``waiting`` batch jobs. After all the configuration - batch jobs restarted and workflow was running normal again.

Hope that helps

V

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

I have exactly the same problem after deleting a user from AD, who, happen to own a batch item. To solve, we have remove the batch own by that person and set again later.

Was this reply helpful? Yes No