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.
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Why: When Salesforce updates a record, it temporarily locks that record to prevent conflicts. Previously, if a flow and another process tried to update the same record at the same time, the flow failed with an UNABLE_TO_LOCK_ROW error. This release reduces these failures by automatically trying again after a short delay.