#12117 [Job Queue] Clearer message and attempt number for runs interrupted by the platform
When the platform interrupts a job queue run, the log entry message now says the run was interrupted by a service restart or update, shows the attempt number, and says a retry is scheduled. The existing 0000PCR telemetry signal gets a JobQueueInterruptedAttempt dimension.
- 2files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-10-02 by darjoo · 2 files (+84 -4), 1 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Replaces confusing ‘job has stopped’ error message with ‘run was interrupted’ message that includes the attempt number
- Derives attempt number from log entries sharing the same System Task Id
- Adds JobQueueInterruptedAttempt dimension to the 0000PCR telemetry signal
- Helps distinguish platform interruptions from actual job failures
- User-facing label text changes require retranslation and updates to any monitoring rules
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 456 “Job Queue Management”, Base Application: modified
Context
- Work items: AB#652242
- Labels: Team: Integrations
- Systems: development
- From the description: “Replaces the message with: “This run (attempt N) was interrupted because the service restarted or was updated.””
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).