Job queue

The job queue in Business Central is the platform's scheduler for background and recurring tasks — nightly batch routines (Adjust Cost — Item Entries, Post Inventory Cost to G/L), scheduled report generation, asynchronous integrations, exchange-rate updates. Each job queue entry has an object to run, a schedule, retry policy, and a user context. Entries can be grouped into job queue categories for concurrency control — serialised categories prevent long-running jobs from overlapping. Failures move to Error status with the captured exception. Telemetry through Application Insights records job runs; healthy operations monitor failed jobs daily.

In practice, the job queue's most common operational failure mode isn't a crashing job, it's a stuck one: an entry left In Process because the session that was running it terminated abnormally (a container restart, a timeout) without the platform's own cleanup catching it. A healthy operations routine checks for entries stuck In Process for longer than their normal run time, not just entries with an explicit Error status, since a stuck job silently stops doing its work without ever showing up as a visible failure.

Where confusion arises: a job queue entry runs under a specific user context, and that user needs sufficient permissions for whatever the job does — a job queue entry configured under a user whose permission set later changes (or whose account is disabled) fails silently at the next scheduled run, often long after the permission change that caused it, which makes root-causing a suddenly-failing nightly batch harder than it should be unless the user context is checked first.