Analytics - Replication jobs can time out if there are many deleted records in the recycle bin
Last updated 2022-02-10 ·Reference W-4693292 ·Reported By 2 users
When there are many deleted records for an object in the organization's recycle bin, Replication jobs for that object may time out. This occurs because the query for the job has to scan through all the deleted records in order to remove deleted records from the dataset.
1) Add an object to Replication that has several million deleted records in the recycle bin
2) Run Replication
3) The job may time out
Empty the organization's recycle bin to ensure there aren't any deleted records affecting the job performance. If the query still times out after this, contact Support.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.