Loading
Feature degradation | Gmail Email delivery failureRead More
Automate Your Business Processes
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Spring ’26 (API Version 66.0)

          Spring ’26 (API Version 66.0)

          These updates affect only flows that are configured to run on API version 66.0 and later.

          Required Editions

          View supported editions.

          Require Visible No-Argument Constructors for Apex Classes

          Custom Apex classes used as invocable action parameters now require an accessible no-argument constructor. These classes typically contain properties annotated with @InvocableVariable. This requirement applies when flows, REST API, or Apex code call invocable actions.

          If your custom Apex class defines other constructors, add an explicit no-argument constructor. Use a public access modifier for classes in your org or within the same package. Use a global access modifier for classes in managed packages to make them accessible from subscriber orgs.

          If a flow references an Apex invocable action with a parameter defined in an Apex class, the system checks for an accessible no-argument constructor. If the Apex class lacks an accessible no-argument constructor, Flow Builder shows an error when you configure that action's inputs.

          Record-Triggered Flows Issue with Non-Insertable Fields Was Fixed

          Record-triggered flows that run before records are saved now respect the internal writeable status of non-insertable fields. If existing flows try to update fields that aren’t editable, this error message appears: Invalid target field for field update.

           
          Loading
          Salesforce Help | Article