Jonathan Gillespie

@TrangOul I agree, it's not exactly the solution I would prefer, but it's the best we can have right now. As far as re-opening this issue/making a new one, that's...

@SoftCreatR that sounds like you have a custom Apex class called `Test` in your org, and it's causing problems during the installation [because `GetFlowMetadata` tries to use `Test.isRunningTest()`](https://github.com/alexed1/LightningFlowComponents/blob/8ff89b72d1aba01bf16bf441d503394beb382155/flow_apps/AnalyzeFlows/force-app/main/default/classes/GetFlowMetadata.cls#L8). I'd try...

Hi @jawills - without seeing your test class, it's hard to say 100% for sure what's going on, but it sounds like your test is mocking a callout, and Nebula...

Hi @erikvlm - you can control that today by setting the value of `Log__c.LogRetentionDate__c` to `null` - the batch purger job ignores any records with a `null`. You could use...

@traguseo good news! I've figured out the source of the bug for this, and I'm hoping to publish a fix for it either this week or next week 🥳 One...

Hi @ihgmpglobant is there any chance you have a stack trace or any other details that you can share? And/or a sample of your code? Offhand, your use case sounds...

@victorramosihg thanks for the details! Do you know which version of the managed package you have installed when that error occurs?

Hi @mbrezina , thanks for reporting this! I hadn't thought of this use case of using a mapping to a restricted picklist field. Luckily, I already have a change (intended...

Hi @erik-malmberg-monfido, there should be another field called "Flow API Name" that you need to set - it should show up just above the "Log Entry message" field in your...

@erik-malmberg-monfido all of those Flow fields on `LogEntry__c` should be auto-set - for some types of Flows, the fields will be blank/`null`, but they're all auto-populated for you.