Answer
A record can be blocked by an active database transaction, while a stale-version error means the saved record changed after it was read. Identify which condition the exact message describes before retrying. An open client page alone does not establish that a database row lock is held.
Work through these checks
- Record the operation, record key, timestamp, environment, and exact error. Distinguish a database lock wait from an optimistic-version conflict.
- Ask the other user or job owner whether an operation is still running. Opening a page alone is not proof that it holds a database row lock.
- Have an authorized administrator inspect the blocking transaction through approved diagnostics. Do not kill sessions or update business tables as a first response.
- After the transaction completes, reload the current record and review the intended change before retrying. Confirm the first attempt did not already create an external effect.