Workflow batch jobs not running

(0) Share

Report

Posted on by Community Member

I have an installation of Dynamics AX 2012 R3 running in a live environment for a client. I have configured the AOS service as a batch server, and i have ran the workflow configuration wizard. Even though the batch jobs are created, they never run. They constantly have a 'waiting status' . How do i fix this? Please help! The situation is slowly turning into a crisis

*This post is locked for comments

I have the same question (0)

All responses (18)

Answers (1)

Suggested answer

Jonathan Halland 11,310 on at

Like (0)

Report

Hi Edward. Is the batch group that your workflow jobs are linked to selected for use on your AOS batch server?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your prompt response. Yes, it is

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

Are you sure they are not running and you've just missed when they did? Do you have workflows setup that should create work items and they didn't?

Was this reply helpful? Yes No
Verified answer

Jonathan Halland 11,310 on at

Like (2)

Report

Hi Edward. My normal checklist is as follows

1. Check that your server configurations in AX are correct and configured as batch. Delete irrelevant ones that may have pulled through when moving environments.

2. Check that the batch group that your batch job is linked to is marked for processing on the correct server.

3. Check that the user that the batch job was created by is valid

4. Check that a full CIL has completed.

5. Check that your workflow execution account is valid

6. Delete batch jobs and recreate.

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

Also, one way to see if they have ran is to enable the 'Save job to history' always (and not just on error). Do this by going on the Workflow message processor job in the Batch jobs form and on the General tab change that option's value to Always. Then you can see in the Batch job history is the job ran.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I did that (setting 'save job to history = always'). There is never any history

Was this reply helpful? Yes No
syed baber 11,633 on at

Like (0)

Report

Hi Edward,

Is the scheduled start date time showing on the batch job or not? Can you paste the screen shot of the batch job showing in 'Waiting' status?

Thanks,

Baber.

Was this reply helpful? Yes No
dekaasboer 1,530 on at

Like (0)

Report

Please verify your server config that your catch server schedule allows jobs to run during the day.

Furthermore, if you are really in a pinch:

Open the AOT, go to forms -> tutorial_workflowprocessor. Click "begin"

This will start to process all workflows immediately. Warning! This will cause a significant slowdown of your PRD system.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

Like (0)

Report

Just an additional note on the remark ' save to history': I would not recommend the setting always for this task as it usually runs every minute. Error only is sufficient. But is you do so, create a procedure to clean up the batch history periodically.

Was this reply helpful? Yes No
Iulian Cordobin 8,201 on at

Like (0)

Report

Yes, indeed the setting to Always for Save to history was just to understand if the job was actually running or not.

Edward - you need to change this setting back to Only error now, and look elsewhere for the errors, as the other members suggested.

Was this reply helpful? Yes No