# Index MongoDB Sync failing after ~3 minutes: "Sync failure: The job has not seen any update for some time.." **URL:** \ **Category:** Elastic Search\ **Tags:** elastic-workplace-search\ **Created:** [March 29, 2023, 5:30pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854 "2023-03-29T17:30:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pocketcolin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pocketcolin/32/117585_2.png) [@pocketcolin](https://discuss.elastic.co/u/pocketcolin)\ **Post date:** [March 29, 2023, 5:30pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854/1 "2023-03-29T17:30:07Z")
I have a Index setup with a MongoDB Connector that is pulling from a collection of ~1.4M records. The initial run was fine and took about 1.5 hours to complete. However, now I'm trying to re-run the sync every day so pull in new records, but when I try to run the sync it fails after about 3 minutes without pulling in any new records. The error I get in the ElasticCloud UI is: ```auto Sync failure: The job has not seen any update for some time.. ``` What does this error mean? I'm interpreting it as meaning the connector tried to find new records but didn't find any after 3 minutes. With such a large collection I'm wondering if the problem is that it's basically timing out after it reviews records in the collection for a few minutes and doesn't find any new ones to add to the index? _Setup_ Host: ElasticCloud Elasticsearch version: 8.6.2 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 30, 2023, 11:14pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854/2 "2023-03-30T23:14:13Z")
Are you using Enterprise Search here? ---
**Author:** ![pocketcolin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pocketcolin/32/117585_2.png) [@pocketcolin](https://discuss.elastic.co/u/pocketcolin)\ **Post date:** [March 31, 2023, 1:53pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854/3 "2023-03-31T13:53:02Z")
Yep! ---
**Author:** ![pocketcolin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pocketcolin/32/117585_2.png) [@pocketcolin](https://discuss.elastic.co/u/pocketcolin)\ **Post date:** [April 4, 2023, 5:50pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854/4 "2023-04-04T17:50:30Z")
For anyone who stumbles upon this issue and is experiencing something similar, Elastic's support responded to me and said they think it might have something to do with the fact that I'm trying to sync \> 500k records. Apparently the connector (which is still in beta) doesn't do well with that many records. They suggested I increase my Enterprise Search from 4GB to 8GB of memory, but that also doubles the hourly cost of my deployment so not the best option for me. I tried increasing the Enterprise Search memory temporarily and that did not fix the issue. I will update this if I get any more information from support. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 2, 2023, 5:50pm UTC](https://discuss.elastic.co/t/index-mongodb-sync-failing-after-3-minutes-sync-failure-the-job-has-not-seen-any-update-for-some-time/328854/5 "2023-05-02T17:50:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.