---
id: change/bcquality/148
type: change
title: "#148 Add Job Queue reliability and scheduling guidance"
summary: Six new performance guidance articles document reliability and scheduling practices for Job Queue and Task Scheduler workloads, including idempotency requirements, UI independence, failure propagation, category-based serialization, on-hold behavior, and duplicate task prevention.
tier: official
language: en
tags:
  - feature
  - main
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:05:28.329Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 8c26ba4e7640fd613e60a40734c744f0f3bda40b
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/148
    title: "microsoft/BCQuality#148: Add Job Queue reliability and scheduling guidance"
    date: "2026-09-14"
    commit: 8c26ba4e7640fd613e60a40734c744f0f3bda40b
    t: null
    quote: These behaviors depend on platform contracts that are easy to misread from otherwise valid AL code.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 148
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/148
kind: pr
base_branch: main
major: null
merged_at: "2026-09-14T10:44:30Z"
author: demiliani
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: feature
behavior_change: false
breaking: false
files:
  count: 24
  additions: 574
  deletions: 25
  al: 21
apps: []
objects_touched: []
objects_unjoined:
  - path: microsoft/knowledge/performance/httpclient-inside-write-transaction-holds-locks.md
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/oncompanyopen-subscribers-must-not-do-io.md
    status: modified
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/skills/review/al-performance-review.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - platform
  - development
quote: These behaviors depend on platform contracts that are easy to misread from otherwise valid AL code.
joined_against:
  major: null
  commit: null
---

# #148 Add Job Queue reliability and scheduling guidance

> Six new performance guidance articles document reliability and scheduling practices for Job Queue and Task Scheduler workloads, including idempotency requirements, UI independence, failure propagation, category-based serialization, on-hold behavior, and duplicate task prevention.

[Pull request](https://github.com/microsoft/BCQuality/pull/148) · merged into `main` on 2026-09-14 by demiliani · 24 files (+574 -25), 21 AL · feature · tier official · reviewed (checked by Opus)

## What changed

- Require external side effects in Job Queue handlers to be idempotent across retries using unique idempotency keys
- Job Queue handlers must be independent of client UI and operate in background sessions
- Execution failures must propagate so the dispatcher can log and retry according to configuration
- Use Job Queue Category Code to serialize jobs that require mutual exclusion
- Putting an entry on hold prevents future runs but does not stop currently executing work, requiring cooperative cancellation

## AL objects touched

- `microsoft/knowledge/performance/httpclient-inside-write-transaction-holds-locks.md`: modified, not in the BC? snapshot
- `microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-category-code-serializes-conflicting-jobs.md`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-external-effects-must-be-idempotent.md`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-not-require-ui.md`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-handlers-must-propagate-failures.md`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/job-queue-on-hold-does-not-stop-running-work.md`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/oncompanyopen-subscribers-must-not-do-io.md`: modified, not in the BC? snapshot
- `microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.bad.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.good.al`: added, not in the BC? snapshot yet
- `microsoft/knowledge/performance/store-scheduled-task-id-to-avoid-duplicate-tasks.md`: added, not in the BC? snapshot yet
- `microsoft/skills/review/al-performance-review.md`: modified, not in the BC? snapshot

## Context

- Systems: platform, development
- From the description: "These behaviors depend on platform contracts that are easy to misread from otherwise valid AL code."

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).