---
schema_version: "1"
id: b12ae7bbea5daed07ff9c44d82dadc715f854333ed35f30b607c5c7412defa3e
title: Catch Missing Required Fields When You Save a Flow
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_automate_flow_builder_catch_missing_required_fields_264.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_catch_missing_required_fields_264.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 69df8b710c47162b901752b4538ec68db56f4e51118b65f3e2430397d51824ca
description: It's now easier to identify missing required fields in Create Records elements when you save a flow. Flow Builder warns you when a Create Records element that uses a record variable is missing an assignment for a required field. Previously, Flow Builder didn't indicate which required fields were missing from a Create Records element. You discovered missing fields only when the flow ran and failed.
products:
  - Cross Cloud
release: "264"
---
# Catch Missing Required Fields When You Save a Flow

It's now easier to identify missing required fields in Create Records elements when you save a flow. Flow Builder warns you when a Create Records element that uses a record variable is missing an assignment for a required field. Previously, Flow Builder didn't indicate which required fields were missing from a Create Records element. You discovered missing fields only when the flow ran and failed.

**Where:** This change applies to Lightning Experience in Professional, Enterprise, Performance, Unlimited, and Developer editions.

**How:** The validation runs automatically when you save a flow in Flow Builder. If a Create Records element is missing a required field assignment on a record variable, Flow Builder shows a warning in the validation panel. Add the missing field assignment, then save again to clear the warning. The validation only checks assignments that it can determine at design time. If the flow populates a required field through an input variable or subflow, the validation can't determine its value until the flow runs.