Reduce record lock errors when Salesforce Maps Advanced optimization jobs update the same parent account records.
Required Editions
| View supported editions. |
Optimization jobs for visit plans run in the background. When multiple jobs update the same parent account records at the same time, record lock errors can occur. To reduce failures, separate competing schedules, reduce overlap across plans, and avoid heavy account updates during optimization windows.
Asynchronous Optimization Risks
Record lock issues are more likely when:
- Multiple visit plans include the same account records.
- You add or remove many users in visit plans.
- Other automations, integrations, or bulk jobs update the same account records.
Scheduled Batch Timing
Salesforce Maps Advanced processes scheduled optimization batches at the start of each hour. Jobs set within the same hour, such as x:15, x:30, or x:45, can run together at the next top of the hour.
Best Practices
- Design visit plans to reduce shared parent account records.
- Schedule at least one hour between optimization runs for plans that share parent accounts.
- Avoid large imports, syncs, or automation updates on account records during optimization windows.
- Monitor optimization status after schedule changes to confirm successful processing.