#11262 Fix retention policy deletion-limit stop propagation
The retention policy deletion limit now stops further policy processing correctly by propagating the stop flag through the temporary setup record after each policy runs, preventing additional limit events after the batch should have ended.
- 3files
- 2AL files
- 2objects
Pull request · merged into main (BC30) on 2026-09-23 by darjoo · 3 files (+105 -0), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- The
EndCurrentRunflag is now transported through the temporary retention policy setup record instead of being lost during isolated codeunit execution - The outer loop can now check the stop condition after each policy completes instead of continuing blindly
- Per-policy error isolation is preserved while allowing proper batch termination
- Added regression test cases covering limit boundary conditions and multiple runs
- No changes to event signatures, scheduling, or the deletion allowance configuration
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 3904 “Apply Retention Policy Impl.”, System Application: modified
- Table 3901 “Retention Policy Setup”, System Application: modified
Context
- Work items: AB#649569
- Labels: AL: System Application, Team: Integrations
- Systems: development
- From the description: “Return the stop flag through the temporary retention policy setup record alongside the deletion count”
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).