Partners struggle with the current Job Queue error logging design.
If there is only one document being posted and if that contains some error, error is shown in the job queue and job queue stops.
While when multiple documents are being posted and some of them contains error, job queue shows success and errors are registered.
This is troublesome because it is often needed that a job runs continuously every half hour and due to this behavior, it is not possible to implement such job queue entries without checking for an error.
It would be great to have the logic re-considered and changed in favor of having the same behavior for single and multiple postings when it comes to error logging.
Comments
The problem is design wise because it was decided to add the error message management behavior directly to the Job Queue Entry instead for example to the Background Posting where I assume this change was coming from.
Removing the possibility to add error message management to existing processes where the job queue is using them as well. Also removing the possibility to add performant queues for repeatable processes where error message management is used in base application or where it was added due to custom processes.
It would be great to change these few lines of code so that the status of a job queue entry would be set to the expected status.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team