What's New: Enhancements to Job Queue (2024 release wave 2)
Job queue enhancements in Business Central 2024 release wave 2: jobs with the same category code now wait in a real queue instead of retrying by polling. The video covers the new "waiting" status, first-in-first-out order, and priority within a category code.
- Introduction and Job Queue Overview
- Job Queue Fundamentals and Category Codes
- Previous Job Queue Behavior and Limitations
- New Queue-Based Execution Model
- Priority Support and Summary
Overview
The video explains how the job queue handled jobs that share a category code before and what changed. Category codes are typically used for sales and purchase order posting, to avoid locking. Previously, a job that found another job running in its category kept retrying, so execution order was effectively random and long waits meant many retries.
Now jobs with the same category code line up in a queue. A waiting job sleeps with the new status “waiting”, and the job that finishes activates the next one in the queue. Jobs run in first-in-first-out order. Priority support lets an urgent job skip ahead within its category code, for example an order with a truck waiting outside. The presenter notes the change was technically already released but belongs to this wave.
Key points
- Jobs with the same job queue category code now line up in a queue and wait their turn, replacing retry-based polling.
- When a job finishes, it activates the next job in the queue.
- A new status, ‘waiting’, shows that a job is sleeping in the queue until its turn.
- Execution order is now first-in-first-out through sequential numbering, instead of the earlier random order from retries.
- Priority support lets a job skip the queue, but only within the same category code; the motivating case was a customer with long posting queues and urgent orders.
- The queueing applies only to jobs sharing a category code, typically sales and purchase order posting used to avoid locking.
- The presenter says the change was technically already released but belongs to 2024 release wave 2.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| Job Queue Category Code Queueing | generally available | 3:19 | “with this wave we technically already released it but it belongs to this” (0:06) |
| Waiting Status for Queued Jobs | status not stated | 3:30 | |
| Job Queue Priority Support | status not stated | 4:27 | |
| Improved Execution Order in Job Queue | status not stated | 4:08 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- other “Job Q Category Code” at 1:13
Quotes
- 0:06 “I would say with this wave we technically already released it but it belongs to this wave”
- 0:32 “it’s not so much a q as it is a way to schedule background tasks”
- 1:13 “there’s one particular field that we are going to touch upon in this presentation which is the um category code job Q category”
- 2:39 “if there a long Q it means you need to call very often like the pizza delivery or doctor you need to try many”
- 3:30 “if there’s a category and someone else is running then we go to sleep so we set status to waiting”
- 3:48 “someone else was running at this time when they’re done they will go out and say activate next next in Q”
- 4:27 “had a lot of sales postings and purchase postings all with very very large orders thousands of lines so each single order would”
- 4:58 “so that’s why we introduced priority as well within that category”
Presenters (as heard): Barrick Nutson.