---
schema_version: "1"
id: d11643180f6bd546d5c7a3588773875b7276f95cb6501348d587144fe3a2c341
title: Spring ’26 (API Version 66.0)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_versioned_updates_66.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_versioned_updates_66.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4c4c29339ae0791cb5fd89265901c628da2cb16ef8fbfa90b2e57ff385473af9
description: These updates affect only flows that are configured to run on API version 66.0 and later.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

## 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.