blog
2026-09-13Winter '272 min read

Salesforce Winter '27 Flow save-time warnings

Flow adds warnings for overlength fixed text and missing required-field assignments, but dynamic values still need run-time tests.

Abstract artwork for the article "Salesforce Winter '27 Flow save-time warnings"

Winter ’27 adds two Flow save-time warnings: overlength fixed text in Assignment elements and missing required-field assignments in Create Records elements that use record variables.

Assignment warnings for fixed text

Catch field length violations when you save a flow adds a warning when an Assignment element sets a record field to fixed text longer than the field’s maximum length. The warning identifies the field and value. Variable references aren’t checked.

Correct the reported literal. Test variable-based assignments separately, with text at the field limit and above it. Check that the value at the limit works and that overlength text follows the expected failure path.

Required-field warnings for record variables

Catch missing required fields when you save a flow adds a warning when a Create Records element uses a record variable that lacks an assignment for a required field. It checks only values Flow Builder can determine at design time, not values supplied by input variables or subflows.

Trace where the required field should be populated before Create Records. Add or correct that assignment.

For dynamic paths, test with the required value missing. Inspect what reaches Create Records, then check the path the flow takes when that value is absent. Both missing required values and overlength text can still cause run-time failures outside the save-time checks’ scope.

Test downstream paths with mock outputs

Flow Builder enhancements and testing tools includes Flow Test Mode (beta), with mock outputs for Action and Subflow elements.

Where those outputs supply text or required-field values, mock overlength text and missing values. Check which downstream path runs and how it handles each case.

Mocks test downstream behavior, not what the dependency actually returns. If success depends on an Action or Subflow response, test the actual response too. Record any dependency path left untested.

Review generated test scenarios

Agentforce for Flow Headless can generate test scenarios for record-triggered, autolaunched, and Data Cloud-triggered flows. It requires the **Agentforce Platform Developer and Admin PSL** and the **Agentforce Developer and Admin Tools permission set**.

If you use it, check the generated scenarios for text at the field limit, text above it, and missing required values. Write or revise tests to cover any gaps.

release items covered