v4.16.3 - Made LogBatchPurger's Batch Size Configurable

[jongpie]

Core Unlocked Package Changes

Fixed #807 by adding the ability to declaratively configure the default batch size in LogBatchPurger. This can be used to reduce the batch size to help with mitigating Apex heap size exceptions that can sometimes happen in the LogBatchPurger job when deleting larger volumes of logging data. And making it now configurable makes it easy to quickly change it in orgs as needed.

• Add new LoggerParameter__mdt record LogBatchPurgerDefaultBatchSize
• ℹ️ The new default batch size for LogBatchPurger is now 500 (and now controlled via LogBatchPurgerDefaultBatchSize).
• Previously, 2000 was used, but 500 is the new default to try to help avoid Apex heap size exceptions. If desired, you can update the record's Value__c field to 2000 to restore the previous value/behavior used prior to this release

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.16.2...v4.16.3

• SF CLI: sf package install --wait 20 --security-type AdminsOnly --package 04tKe0000011Mr1IAE
• Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe0000011Mr1IAE
• Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe0000011Mr1IAE

---

This discussion was created from the release v4.16.3 - Made LogBatchPurger's Batch Size Configurable.