Unable to log entries in Nebula via Omnistudio

[gokhalesamruddhi]

Package Edition of Nebula Logger

Managed Package

Package Version of Nebula Logger

v4.15

New Bug Summary

While calling the apex remote class CallableLogger from omnistudio, we're getting this error "Can not get instance of Class CallableLogger". The calls do work through anonymous apex indicating it is not an issue with the package version. Please refer to the attached screenshots.

[jongpie]

Hi @gokhalesamruddhi - this looks like it could be an issue with how the class name has been configured within the remote properties - the class name for the managed package needs to be Nebula.CallableLogger (with a . instead of __). I was able to do a quick test of this in a scratch org, and everything seems to be working as expected.

[gokhalesamruddhi]

Hi @jongpie , thanks for the input. I tried the same in our org but still getting an error. Please see attached screenshot.

[jongpie]

Hi @gokhalesamruddhi - I've been trying to reproduce this issue, but so far, I haven't had any luck (it seems to work ok for me). Given that you're using the managed package, it's also a little harder to troubleshoot this issue because Salesforce obfuscates some of the details of managed packages.

To try to help figure out the source of this error, could you try updating a custom metadata record in your org? Under Setup --> Custom Metadata Types --> Logger Parameters (LoggerParameter__mdt object), update the record EnableStackTraceParsing to have a value of false (it defaults to true, shown in the screenshot below).

Once you've done that, try again in OmniStudio to see if you still get that null pointer exception

[gokhalesamruddhi]

Hi @jongpie , I tried it but it still gives the same message.

[jongpie]

@gokhalesamruddhi I was finally able to reproduce & fix this issue! I have a few other (unrelated) changes to wrap up, but I'm planning to release the changes sometime next week.