If requesting support, please provide the following details to help troubleshooting: Error message: Qty. to Handle (Base) in the item tracking assigned to the document line for item 800307 is currently 15. It must be 1. Check the assignment for serial number SC2505130074, lot number PSW2505160001, package number . Internal session ID: 80f0c1ee-74d4-47d9-a8e8-f107ea632a47 Application Insights session ID: 07ecf955-d8a2-4799-9fb6-5526ef16f201 Client activity id: 151961c2-2c0d-40e5-8437-b3165b350769 Time stamp on error: 2025-05-20T08:37:18.5769733Z User telemetry id: acd429df-72ec-4aaa-b25e-d02a7a3fe033 AL call stack: "Tracking Specification"(Table 336).TestFieldError line 12 - Base Application by Microsoft "Item Jnl.-Post Line"(CodeUnit 22).SetupSplitJnlLine line 73 - Base Application by Microsoft "Item Jnl.-Post Line"(CodeUnit 22).PostSplitJnlLine line 4 - Base Application by Microsoft "Item Jnl.-Post Line"(CodeUnit 22).RunWithCheck line 16 - Base Application by Microsoft "Prod. Order Status Management"(CodeUnit 5407).PostFlushItemJnlLine line 10 - Base Application by Microsoft "Prod. Order Status Management"(CodeUnit 5407).FlushProdOrderProcessProdOrderRtngLine line 57 - Base Application by Microsoft "Prod. Order Status Management"(CodeUnit 5407).FlushProdOrder line 43 - Base Application by Microsoft "Prod. Order Status Management"(CodeUnit 5407).ChangeProdOrderStatus line 12 - Base Application by Microsoft "Prod. Order Status Management"(CodeUnit 5407).OnRun(Trigger) line 14 - Base Application by Microsoft "Released Production Order"(Page 99000831)."Change &Status - OnAction"(Trigger) line 3 - Base Application by Microsoft
If possible, review or trace the codeunit or process being executed by the job queue. It may not be committing the transactions correctly or might be leaving behind orphaned tracking lines or reservation entries. There could be a need to include logic that explicitly resets, validates, or clears item tracking lines before each execution to prevent this accumulation of errors. If you're not able to debug this yourself, it’s highly recommended to contact your Business Central partner or a technical consultant who can analyze the job queue logic through the AL code or event subscriptions. They can help implement safeguards to prevent unprocessed or partially processed tracking lines from persisting across multiple job queue cycles. Debugging in a sandbox environment with the same setup could also help pinpoint where the breakdown is happening. Hope debugging into system will resolve your query! Regards, Mansi Soni
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Rishabh Kanaskar 4,232
Nimsara Jayathilaka. 2,863
Sumit Singh 2,819