Winter '26 - Nebula Logger Not Allowed in Sync Path post update.

[shuylern]

Anyone else having an issue with this new feature?

This drastically changes our Flow patterns involving Nebula Logger.

https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_enforce_perm_requirements_on_built_in_apex_classes.htm&release=258&type=5

[augustoZaelot]

I'm facing an issue adding a new "Add Log Entry" action to flows, but the existing ones do not present any error.
Existing action:

Copy of existing action:

Newly created action:

[shuylern]

That is the same error I am receiving.

[augustoZaelot]

Weirdly enough, the error message displayed to us when trying to save the new flow version is not present anywhere in salesforce docs. I'll keep digging and will try to find a workaround.

[jamessimone]

That warning is displaying when it shouldn't be and the Flow team is going to fix this ASAP. Things will continue to work, so you're safe to ignore the warning for now. You should still be able to save through the warning; that's what we have heard from the Flow team.

[augustoZaelot]

Thank you for your answer, @jamessimone. I tested it with a simple class returning a boolean and got the same message, so I thought it was just a bug. I really appreciate you taking the time to clarify this.

[admillican08]

Hi, I was not able to ignore the warning. I tried saving and activating a record-triggered flow with the Nebula-Logging action in the "Run Immediately" path and Salesforce did not let me activate it. But, I found an interesting workaround. I went into the Log action, opened the "Advanced Settings", then went into "Transaction Control". By changing the Transaction Control option to "Always continue in current transaction", I was able to then save without a warning and to activate the flow

[jongpie]

@admillican08 thanks for sharing the workaround! @jkranz-rk (one of the Flow product managers at Salesforce) reached out suggesting the same solution as a workaround, so this seems like the best course of action for now, until Salesforce patches the issue.

[sjames-hms]

@jongpie This is a helpful thread. Can we confirm that all existing apex actions for Log An Entry don't need to be reviewed and this only impacts new apex actions? Also, has there been any updates on the Salesforce fix? Thank you.

[augustoZaelot]

@sjames-hms None of my existing Apex Actions for nebula had any impact. And only the new ones will throw this error.

Regarding the fix, there is only the workaround above. I'm still getting the error in my preview sandbox.

[jkranz-rk]

@sjames-hms The fix has indeed been rolled out and I'm no longer able to reproduce the issue. Please let me know if you find that it may still be impacting you!

[sjames-hms]

I just double checked in my preview orgs and I'm not seeing the issue. Thanks for providing an update.

[jkranz-rk]

For anyone following this thread, the fix was pushed in the patch release that went out a couple weeks ago, and I've verified in a couple preview dev orgs that I'm not getting the issue anymore. If you think you're still running into the issue, please let me know!