I am unable to save a Flow with an Apex Action after the Salesforce Winter ‘26 release. What should I do?
Question
After the Salesforce Winter ‘26 release, when I try to add an Apex Action to the Run Immediately path on a record-triggered Flow, I can’t save the Flow. The following error appears:
“A record-triggered flow’s Run Immediately path can’t execute transaction-controlled actions. Remove this element from the flow, or move it to a scheduled path.”
Answer
This change is expected behavior introduced in Winter ‘26. Transaction-controlled actions (such as Apex Actions with certain settings) are no longer supported in the Run Immediately path. They must be placed in an asynchronous path instead.
⚠️ Important:
This rule applies to all new Flows created from Winter ‘26 onwards. Flows created before the Winter ‘26 release will continue to work as-is until further notice from Salesforce.
How to fix the error
- Open your Flow in Salesforce.
- Select the Apex Action Element.
- Click Show advanced options.
- Under Transaction Control, set the option to Always continue in current transaction.
- ⚠️ If you choose either of the other two options, the Flow will not save, and the error will continue.
Important Notes:
- Always continue in the current transaction means the action will run in the same transaction.
- If the Apex Action makes a callout while there are pending operations, the Flow will fail.
- If your use case requires callouts or asynchronous handling, you must add an Asynchronous Path in the Flow’s Start element and place the Apex Action there.
Additional Resources:
Salesforce Knowledge Article: Unable to Save Flow with Apex Action in Immediate Path After Winter ‘26 release
0 Comments
Add your comment