# Feed Overlapping Issues.

**URL:** <https://support.prodi.gy/t/feed-overlapping-issues/6841>\
**Category:** Uncategorized\
**Created:** [October 11, 2023, 8:05am UTC](https://support.prodi.gy/t/feed-overlapping-issues/6841 "2023-10-11T08:05:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [October 11, 2023, 11:47am UTC](https://support.prodi.gy/t/feed-overlapping-issues/6841/2 "2023-10-11T11:47:31Z")

</div>

hi @axsmarine!

Thanks for your message and welcome to the Prodigy community 👋

Have you seen my post on post on duplicate or missing data?

> [@Help! I have duplicates or missing data: Best practices on accounting for annotations](https://support.prodi.gy/t/help-i-have-duplicates-or-missing-data-best-practices-on-accounting-for-annotations/6704):
>
> Scaling annotations can be really hard. More scale means more complexity, which can make accounting for all of those annotations challenging, time-consuming, overwhelming, error-prone, or even impractical. Unfortunately, many ML engineers and developers don’t realize this until they scale their annotations, risking wasted time and effort after labeling hundreds or thousands of annotations. As you dig deeper, you'll also find trade-offs from memory to network/latency to human-centered issues wit…

One thing I suspect it could be is [work stealing](https://prodi.gy/docs/task-routing#work-stealing). I noticed you have that in your config (`"allow_work_stealing": false,`) but that wasn't implemented until [v1.12.0](https://prodi.gy/docs/changelog#v1.12.0). Since you're using v1.11.11, can you upgrade to `v1.12.7` and retry?

But be aware - work stealing may sound like something you don't want, it is a preventive mechanism to avoid the loss of records in a stream, which can be much worse than duplicates!

The docs explain this well:

> Without work stealing you might be able to guarantee annotations occur _at most once_ while accepting losing a few examples in the process. By enabling work stealing you ensure **all examples** will be annotated in the data stream **at least once**.

Unfortunately, the best answer is better training for your annotators to save their annotations when they're done and close out browser windows when they're done.

One other point -- won't contribute to your issue -- is that `"force_stream_order": true` won't do anything as it was [deprecated](https://prodi.gy/docs/changelog#v1.11.0) in v1.11.0.

Hope this helps!

---

_[View the full topic](https://support.prodi.gy/t/feed-overlapping-issues/6841)._
