-
-
Notifications
You must be signed in to change notification settings - Fork 242
Handle DELETE_OPERATION_TOO_LARGE exception #1026
Copy link
Copy link
Open
Labels
Feature: Log RetentionItems related to LogBatchPurger or LogBatchPurgeSchedulerItems related to LogBatchPurger or LogBatchPurgeSchedulerLayer: ConfigurationItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeType: BugSomething isn't workingSomething isn't working
Description
Activity
Metadata
Metadata
Assignees
Labels
Feature: Log RetentionItems related to LogBatchPurger or LogBatchPurgeSchedulerItems related to LogBatchPurger or LogBatchPurgeSchedulerLayer: ConfigurationItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeType: BugSomething isn't workingSomething isn't working
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
v4.19.3
New Bug Summary
Periodically receive Apex unhandled exceptions during scheduled purge batch window that delete failed due to DELETE_OPERATION_TOO_LARGE, Cascade deleting too many records for both Feed Items and Log Entries.
The log records (and child log entries) are deleted by the time I review the unhandled exceptions.
IFF the eventual deletion of the parent logs is guaranteed, would be great to handle (WARN/ERROR log?) these currently unhandled exceptions.