Null Pointer when logging inside of an autolaunched, platform-event handled flow

[dschibster]

Package Edition of Nebula Logger

Unlocked Package

Package Version of Nebula Logger

v. 4.19.1

New Bug Summary

Hi @jongpie!

We tried implementing Nebula Logger to find an issue where sometimes a Platform Event would not process properly. The order is as follows:

Platform Event -> Trigger Actions Framework -> Autolaunched Flow

Inside of the Autolaunched Flow I tried logging with FlowLogger, but even the first Log Entry, only containing a Scenario Name, Flow Name and Log Message, ran into an NPE:

System.NullPointerException: Attempt to de-reference a null object

Class.FlowLogger.LogEntry.addToLoggerBuffer: line 140, column 1
Class.FlowLogEntry.addFlowEntries: line 99, column 1
11:19:13.231 (6704472979)|FATAL_ERROR|System.NullPointerException: Attempt to de-reference a null object

Class.FlowLogger.LogEntry.addToLoggerBuffer: line 140, column 1
Class.FlowLogEntry.addFlowEntries: line 99, column 1

These were the input params:

Need pointers about the problem here. Or is this a genuine bug?