Async Failure Additions plugin
The Async Failure Additions plugin adds extra context to log entries generated by failed asynchronous jobs - queueable, batchable, and scheduled jobs. Useful when investigating async failures where the default entry doesn’t carry enough context.
What it adds
- A trigger plugin on
LogEntry__c(orLogEntryEvent__e, depending on the shipped version) that detects entries produced by async-job failures. - Enrichment logic that adds extra fields to those entries - typically async job type, job ID, and additional platform context.
Installation
Ships as its own unlocked package. Install after the core Nebula Logger unlocked package. See the GitHub releases page for the current package ID.
When to use it
- Orgs with lots of async jobs (integrations, scheduled work, event-driven batches) where async failures are a common investigation type.
- Cases where the default log entry for a failed async job doesn’t tell you enough about which job failed.
Configuration
The plugin is opt-in - once installed, ensure its LoggerPlugin__mdt record has IsEnabled__c = true.
Beyond enabling it, most configuration lives in the plugin’s own README under nebula-logger/plugins/async-failure-additions - check there for the current list of enrichment fields and any tuning options.
Where next
- Async Failure Additions plugin reference - auto-generated Apex reference.
- Plugin framework overview - how plugins hook in.
- Logging Guide - Apex - Async parent/child linking - manual pattern for correlating async logs.