Change batch job status to error based on Batch error log

(0) Share

Report

Posted on by Navneeth Nagrajan

2,585 Super User 2026 Season 1

Hi All,

We have a scenario where we need to parse through all the batch job history details and set the status of the batch job to error, set the status of the batch job to error, if the batch log has errors in it. As per standard Ax or Operations, the batch job task, if marked as ended, sets the entire batch to Ended. Instead, if the all the batch job tasks are marked as Ended, and if there is an error in the log, the entire batch should be set to Error status, instead of Ended.

I was successful in fetching the error details of the batch job from the log, but what's the best practice to set the batch job status to error, if there are error logs in the batch tasks log or the batch log?

I have used the SysInfologEnumerotor, to fetch the details of the batch log, but while setting the batch job status to error, the AOS crashes. The approach that I have used is fetch the error log and based on the error log, update the status in the BatchJob table to Error. Later, I have added this method as an event handler in the BatchJob table's update() method, as a post event handler. Is this the right approach? Please correct me, if I am wrong.

For example, let's say I have created a movement journal TEST_001 and added it to the batch queue. The movement journal processes successfully with all the lines successfully processed, but if there are errors in the log, then the whole batch status for the movement journal should be set to Error.

Thanks in advance.

Regards,

Navneeth.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Martin Dráb 239,253 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What's the point of handing all errors, let everything to get into Ended state instead of Error and then digging into infolog and trying to reimplement what the framework would do for you?

Why don't you simply throw an exception from the failing tasks and let AX to handle the rest for you? That's the best practice.

Was this reply helpful? Yes No
Navneeth Nagrajan 2,585 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

Thanks for the suggestion.

All the exceptions are caught for the failing tasks. As per standard Ax functionality, if any of the tasks is set to Ended and if the infolog for that task has an error, then the entire batch is set to Ended. The requirement is if the infolog for that task or for any of the tasks has an error, the batch status should be set to Error, instead of Ended. The batch, as per standard Ax, is set to Ended which is not what's required, in this case.

Regards,

Navneeth.

Was this reply helpful? Yes No
Martin Dráb 239,253 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Yes, I understand it and I believe that "All the exceptions are caught for the failing tasks" is the bug. If you don't swallow all exceptions, the task will fail and therefore the whole batch. That's how it normally works, but your handling of all exceptions breaks it. Throw an exception if a task fails.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (1)

Report
Copy link

Link copied!

You typically store in the global variable scope or in the task management thread if there were any errors during execution if they are handled in a try-catch block for sub-tasks.

All you need to do is to check if the global variable is set to true (in case an error has occurred), then throw the error as Operation has failed or similar in the controller thread.

Alternative solution is to set a dependent batch task which can be triggered in case one of the tasks had an error, and do a throw there.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Navneeth,

How did you come across this issue..?

Was this reply helpful? Yes No