---
schema_version: "1"
id: d2b3f04bacf53272023bb9998fc45953bf30e953626df35154abd1a295c21c4c
title: Reduce Flow Failures Caused by Record Lock Contention
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_row_lock_retry_264.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_row_lock_retry_264.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 293ae5ade4f014f68ca1c4f9762ec25e0288a08a0bbc4b38af3347239cae3e71
description: 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.
products:
  - Cross Cloud
release: "264"
---
# 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.

**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.