Data loaded Account Territory Loader (ATL) records are not working properly. The AccountShare records are not deleted or created after the insert or upsert data load job.
The ATL records are not updated due to the large data loading batch size. If the batch size is larger than 20, a trigger copies the territory from the ATL fields and causes the AccountShare records to not fire. This is because the Salesforce query limit is already reached.
Use a smaller batch size during the data loading. The optimal batch size is approximately 10-20.
CRM help: Territory Management using ATL
Salesforce guide: Execution Governors And Limits
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.