Jonathan Gillespie

@dominykasvitkus I think that issue has come up a few times before, and seems to be a limitation on the Flow side / I'm not sure if there's much that...

Hi @JaskiratSinghIH - at the moment, I don't expect to work on this for at least several months. There are several challenges with making this work in Flow, including: -...

Hi @JaskiratSinghIH at the moment, I still haven't found a good approach that will work in Flow. The combination of some UI limitations in Flow + the lack of support...

@twentyTwo that would be amazing! Feel free to submit a PR for this at your convenience, and let me know if you have any questions along the way

@vikashkrml sure, that sounds great!

@twentyTwo no worries at all, and no need to apologize! It's open source work, there's no pressure to contribute! If/when you'd like to contribute to another item in the future,...

This is now available in [release `v4.16.5`](https://github.com/jongpie/NebulaLogger/releases/tag/v4.16.5)! Once the version has been installed, the Apex cursor transaction limits will be automatically tracked on `LogEntryEvent__e` and `LogEntry__c`.

Hi @dominykasvitkus - if you want to prevent the logs from showing up in the browser's console, there's a settings field you can use to control that (`LoggerSettings__c.IsJavaScriptConsoleLoggingEnabled__c`). For production...

@dominykasvitkus thanks for the clarification! I see what you're saying about the initial message not checking the settings first. I'm not planning to expose the functions `enableSystemMessages()` and `disableSystemMessages()` (I...

@dominykasvitkus I've just published [release `v4.16.4`](https://github.com/jongpie/NebulaLogger/releases/tag/v4.16.4) to address this. It will now check `LoggerSettings__c.IsJavaScriptConsoleLoggingEnabled__c` first, before deciding if it should print the initialization and error messages in the browser's console....