We have a background processing that processes data for a customer. Now the processing encounters an error. However, this error is not reported back as a RunTime error.

Instead, this dimension combination error is written to an "Error Message" table and an actual RunTime error is not triggered.

Task queue processing retrieves this entry upon completion and then throws the RunTime error.

As a result, this error cannot be caught using Codeunit.run (as implemented in BossInterface), since this is only thrown after BossInterface processing.

Analyzing error handling in code for dimension combination check in Codeunit 408 “Dimension Management” with function LogError and the handling of it in Codeunit 448 “Job Queue Dispatcher” running a codeunit with a job queue entry and try to catch all errors, which occur while processing different code pieces (processes). One of it is posting a delivery. As the error should be logged in a record (example: added table called “Boss Interface Message”), the job queue entry should never fall on an error. With this kind of handling the error in NAV (logging/saving the error and setting the job queue entry on error when any error was saved in the run process), it is not possible to catch all the errors anymore within an object run by the job queue entry.