Catch field length violations when you save a flow, before they cause run-time failures. Find missing required fields in Create Records elements at save time. Reduce limit failures in scheduled flows with dynamic batch sizing. Automatically retry flows that hit record lock contention.
- Catch Field Length Violations When You Save a Flow
Avoid run-time failures by validating field length constraints when you design and save a flow. If a Create Record or Update Record element sets a record field to a text value that's too long, Flow Builder shows a warning. By identifying the specific field and the value that exceeds the limit, this validation helps you catch configuration errors before they cause run-time failures. - 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. - Reduce Flow Failures Caused by Record Lock Contention
Flows automatically try again when they encounter a record lock error during transaction initialization. When multiple processes try to update the same record simultaneously, the flow waits 10 seconds and makes one more try. This delay gives the other process time to complete and release the lock. This change applies to schedule-triggered flows with run-time API version 62.0 or lesser.