Workflow approval tasks does not finish

(0) Share

Report

Posted on by Jose Alonso Foubelo

Hi all!

We have a problem in a customer production environment, with Microsoft Dynamics AX 2012 R3. We have set up multiple workflows of PurchTableTemplate and PurchReqReview type. These workflows worked fine, but some days ago we have started to detect an unexpected behavior.

In some instance of any of this Workflows when there is an approval tasks and the users approves it, the work item is approved (we can see it in the detail of the workflow execution), but the system doesn't create the step finished item, and the approval task doesn't finish. This behavior is absolutly random. The workflow instances with this problem have no any work ítem pending, no any user has the workflow instance asigned, but it continues like "pending" and there is no any action to do with them.

Because of this , the instance is still in "pending" status , but it is as if it was stopped, since it not advance and we can not make any operation on it.

Has anyone detected a similar behavior?

I attach the workflow history of one of this instances to better understanding of the problem.

Overview (status pending):

WFDetail overview (no user asigned):

WFDetail work items (no pending work item):

WFDetail tracking details (Approval, completed):

WFDetail tracking details (Approval with work item approved, but never completed):

Thanks in advance

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

Verified answer

André Arnaud de Cal... 300,904 Super User 2025 Season 2 on at

Like (1)

Report

Hi Jose,

Can you check the history of the batch job for workflow processing? There might be an issue that it will fail every ten minutes. You can review the log to actually see what is happening.

You can also check the table SysWorkflowMessageTable. This is a work list for the batch job. If the field batch affinity has a value other than an empty GUID and the MessageLifeCycleState is Queued you have to check the ModifiedDateTime field. Check if this date is prior to the current or last batch run. If so, there might be an issue with one or more of the tasks.

There is a retry every 10 minutes. Then older tasks with a batch affinity filled and modified date/time older than 10 minutes will also be picked up together with new workflow messages. Depending on the issue it will fail again together with new messages. Then the list of workflows which "hangs" will grow and grow every 10 minutes.

Was this reply helpful? Yes No
Jose Alonso Foubelo 40 on at

Like (0)

Report

Hi André,

First of all, thanks for your answer.

I have checked the history of the batch job as you suggested, and I can see the error every ten minutes (more or less). I have taken a look to the log, but it doesn't give so many information (or I am not able to find it), such as the incorrect register that generates the error.

This is the error log I get:

I have changed the language to en-us but some lines still appear in Spanish, I can try to translate them if you think they can give us more important information. The call stack is:

Microsoft.Dynamics.Ax.Xpp.ErrorException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.ErrorException' was thrown.

   at Dynamics.Ax.Application.WorkflowTrackingTable.saveTracking(SysWorkflowTracking _tracking) in WorkflowTrackingTable.saveTracking.xpp:line 147

   at Dynamics.Ax.Application.SysWorkflow.faultWorkflowInstance(SysWorkflowTable _workflowTable, String _user, String _faultMessage) in SysWorkflow.faultWorkflowInstance.xpp:line 74

   at Dynamics.Ax.Application.SysWorkflow.internalFault(WorkflowContext _workflowContext, String _user, String _faultMessage) in SysWorkflow.internalFault.xpp:line 56

   at Dynamics.Ax.Application.SysWorkflow.fault(WorkflowContext _workflowContext, String _user, String _faultMessage) in SysWorkflow.fault.xpp:line 32

   at Dynamics.Ax.Application.SysWorkflowQueue.dispatch(Guid _affinity) in SysWorkflowQueue.dispatch.xpp:line 185

   at Dynamics.Ax.Application.SysWorkflowQueueTask.Run() in SysWorkflowQueueTask.run.xpp:line 13

   at Dynamics.Ax.Application.BatchRun.runJobStaticCode(Int64 batchId) in BatchRun.runJobStaticCode.xpp:line 54

   at Dynamics.Ax.Application.BatchRun.runJobStatic(Int64 batchId) in BatchRun.runJobStatic.xpp:line 13

   at BatchRun::runJobStatic(Object[] )

   at Microsoft.Dynamics.Ax.Xpp.ReflectionCallHelper.MakeStaticCall(Type type, String MethodName, Object[] parameters)

   at BatchIL.taskThreadEntry(Object threadArg)

Any idea?

Was this reply helpful? Yes No
Jose Alonso Foubelo 40 on at

Like (0)

Report

Hi again André,

I have been investigating SysWorkflowMessageTable and I think I have found the line that makes the error occurs: there is one task for VendDisbursementTemplate with a WorkflowContextRecId that already does not exist in the LedgarJournalTable.

I suppose that if I delete that line, the error would desappear, but... will be neccesary to delete the register in the SysWorkflowTable too?

Was this reply helpful? Yes No
Verified answer

Jose Alonso Foubelo 40 on at

Like (1)

Report

Finally, we deleted the wrong records on SysWorkflowMessageTable as André indicated in another post:

community.dynamics.com/.../195136

Workflows work ok again.

Thanks André!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

HI

Was this reply helpful? Yes No
PK Axapta 140 on at

Like (0)

Report

Hi Jose, I am also facing the same issue - batch job erroring out after every 10 mins. Could you please share some steps or details, how you resolved this.

Many thanks in advance!!

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

Like (0)

Report

Hi Pankaj,

You also created a new question on the forum. Let's continue on you new post.

community.dynamics.com/.../290036

Was this reply helpful? Yes No