Found issue in Error Logging

[jayeshtejwani]

Hi @jamessimone,

Starting as a discussion but may be this is an issue.
I am running the rollups on parent object Account. I have written a custom logging class to log catch the errors thrown during Account Update in our custom object. To test if errors are being logged, I create null pointer exception in AccountTriggerHandler(before update), and that's seen in debug logs but not caught or displayed by RollUp Logger or Custom Logger class, which doesn't help.

Extended Class

Debug Logs from the Custom Logger Debug Statement

Success Printed for a failed transaction. Debug Logs of the FlowOutput(received after List<Rollup.FlowOutput> innerOutputs = Rollup.performRollup(flowInputList);)

Null Pointer exception

[jamessimone]

@jayeshtejwani the default behavior of the included logger is to only print messages to the apex debug logs. I would look at the implementation for the actual Custom Object logger if you’re interested in seeing how to save the logged inputs to a custom object. Not all logging within Apex Rollup is going to be logged in the event of an uncaught exception, but the example you’re using is with an exception outside of Apex Rollup, so … it has to be caught/handled outside of Apex Rollup. The library isn’t mean to be an end-all logging solution for the rest of your org, or for problems that occur elsewhere in your flows/Apex. For that, I would highly recommend the usage of Nebula Logger.