You are here:
Troubleshoot REQUIRED_FIELD_MISSING Errors in Flows
When a flow attempts to create or update a record without populating all required fields, you receive a REQUIRED_FIELD_MISSING error.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To open, edit, create, activate or deactivate a flow using all flow types, elements, and features available in Flow Builder, including Einstein and Agentforce for Flow: | Manage Flow |
| To view object field definitions: | View Setup and Configuration |
| To view debug logs: | View All Data |
The REQUIRED_FIELD_MISSING error occurs when a flow tries to create or update a Salesforce record but doesn't provide values for all fields marked as required. This error can occur in various flow scenarios and contexts.
To troubleshoot and resolve this error:
- Understand the common scenarios that cause this error
- Identify which field is missing
- Find all the required fields for an object
- Apply solutions and recommendations to prevent the error
- Problems, Solutions, and Prevention Techniques for Required Field Errors
Identify common required field problems, apply solutions, and follow prevention techniques to avoid REQUIRED_FIELD_MISSING errors. - Identify Which Field Is Missing
When you receive a REQUIRED_FIELD_MISSING error, use these techniques to identify which field caused the error. - Find Required Fields for an Object
To prevent REQUIRED_FIELD_MISSING errors, before building a flow, identify the required fields for the object's records. There are two options: use Schema Builder or create a record on the object, but don't save it. Either option shows the required fields, but Schema Builder also shows system populated fields that you don't include in a flow.
See Also
Problems, Solutions, and Prevention Techniques for Required Field Errors
Identify common required field problems, apply solutions, and follow prevention techniques to avoid REQUIRED_FIELD_MISSING errors.
This table provides a reference for troubleshooting required field errors. Each row describes a common problem, the solution to fix it, and techniques to prevent it in future flows.
| Problem | Solution | Prevention Technique |
|---|---|---|
Creating Records Without All Required Fields When using a Create Records element, Flow Builder doesn't indicate which fields the object requires. If you don't manually set all the required fields, the flow fails at run time. Example: A flow creates a Contact record but doesn't populate the required Last Name field. |
Check Required Fields Before Building Before you configure a Create Records or Update Records element, check the object's required fields in Object Manager. Populate all required fields either directly in the element, through Assignment elements, or from screen input. Alternatively, a Quick Action element of type Create shows which fields the action layout requires. However, Quick Action elements limit available fields to the action layout and don't store the created record's ID. Set default values for required fields if you're not populating them in another way within the flow. |
Maintain a checklist of required fields for objects commonly used in your flows. Consult Object Manager or the object's page layout before building flows that create or update records. |
Screen Flows Not Populating Required Fields When a screen flow collects information to create a record, required fields can go unpopulated if the screen doesn't include them and the flow doesn't set them in another way. Example: A screen flow for creating Cases includes fields for Subject and Description, but the screen doesn't include the required Status field, and the Create Records element doesn't set it. |
Add Required Fields to the Screen or Populate Them in the Flow Add record fields directly from the object to the screen. Record fields automatically inherit their requiredness from the object definition. For required fields that users don't set, populate them directly in the Create Records element or with an Assignment element earlier in the flow. |
When designing screen flows, review the object definition in Object Manager to identify all required fields. Add required fields to the screen, or provide default values in the flow for fields users don't set. |
Screen Flow Updates Clearing Required Fields In a screen flow, if a user leaves a field blank and the flow uses that blank value to update a record, the update overwrites the existing value with blank. If that field is required, the update fails. Example: A screen flow makes it possible for users to edit Account fields. A user leaves the Company field blank. The Update Records element uses the blank screen value to update the Company field, which fails because Company is required. |
Make Screen Fields Required or Use a Decision Mark screen components for required fields as required so users can't leave them blank. For optional screen fields that update required record fields, use a Decision element to check whether the value is blank. If blank, route to a different Update Records element that updates only the other fields. |
Test update operations with various record states to make sure that the required fields remain populated. Identify which screen fields map to required record fields and mark them as required on the screen. |
Record Type and Validation Rule Requirements Different record types can have different required fields. Validation rules can also make fields conditionally required. A flow can work for one record type but fail for another. Example: A flow creates opportunities with the "Enterprise" record type, which requires more custom fields that the "Standard" record type doesn't require. |
Test with Multiple Record Types If your object has record types and the flow creates records of multiple record types, test the flow with each record type to make sure that the flow populates all type-specific required fields. Use decision elements to handle different record types with different logic paths if needed. |
Document the record types and validation rules that affect your flows. Review field requiredness for each record type during flow design. Include record type testing in your flow testing checklist. |
General Prevention Guidelines
- Implement fault paths: Add a fault path to Create Records and Update Records elements. Use the fault path to show a helpful error message to users or to log the error for Salesforce admin review.
- Test thoroughly before activation: Use Debug mode to test the flow with various data scenarios, including edge cases where some fields can be empty.
- Use description fields: Add descriptions to your flow elements noting which required fields the flow populates and where the values come from.
- Monitor flow errors: Regularly review flow error emails and logs to catch issues early.
Identify Which Field Is Missing
When you receive a REQUIRED_FIELD_MISSING error, use these techniques to identify which field caused the error.
-
Check the error message.
The REQUIRED_FIELD_MISSING error usually specifies which field was missing. Look for the field API name in the error details.
-
Use debug mode.
Run the flow in debug mode and examine the debug details when the error occurs. The debug log shows which element failed and includes the specific field name. For more information, see Test or Troubleshoot Flows With the Flow Builder Debugger.
-
Review Apex debug logs.
For record-triggered flows, check the Apex debug logs. Search for "REQUIRED_FIELD_MISSING" to find the exact field that caused the failure.
-
Check email notifications.
Flow error emails sent to the flow owner include the field name and error details.
Find Required Fields for an Object
To prevent REQUIRED_FIELD_MISSING errors, before building a flow, identify the required fields for the object's records. There are two options: use Schema Builder or create a record on the object, but don't save it. Either option shows the required fields, but Schema Builder also shows system populated fields that you don't include in a flow.
To review required fields in Schema Builder, follow these steps.
Before building a flow, identify the required fields for the object's records. There are two options: use Schema Builder or create a record on the object, but don't save it. Either option shows the required fields, but Schema Builder also shows system populated fields that you don't include in a flow.
You now have a list of required fields for the object. Use this information when building flows to make sure that you populate all required fields.
