In Dynamics AX 2012, there are times when batch jobs appear to be stranded in a waiting status. When this happens, the cause can typically be a batch server or batch group which is not set up properly. However, if these are set up correctly and you see one or more jobs with a status of “Executing” while others remain in a “Waiting” status, it could be that the maximum number of threads has been reached.
To confirm, click on each job that is executing and then click on “View Tasks” and note the number of tasks executing. If the total number of tasks executing is equal to the maximum number of threads designated on the Batch Server setup form, the other batch jobs will remain in a “Waiting” status until some tasks have completed.
Refer to the Dynamics AX 2012 Batch Overview for more information on configuring a batch server and adjusting the maximum batch threads.