# Repeated Examples in Multi-user Sessions **URL:** https://support.prodi.gy/t/repeated-examples-in-multi-user-sessions/5235 **Category:** Uncategorized **Tags:** streams **Created:** [January 25, 2022, 11:43pm UTC](https://support.prodi.gy/t/repeated-examples-in-multi-user-sessions/5235 "2022-01-25T23:43:09Z") **Posts on this page:** 1 **Showing post:** 4
### Author: ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines) #### Post date: [January 28, 2022, 10:21am UTC](https://support.prodi.gy/t/repeated-examples-in-multi-user-sessions/5235/4 "2022-01-28T10:21:25Z")
> [@rz789](#): > > So I wonder, can we turn off the ""work stealing" mechanism" as you mentioned above, and what effect would it cause for the multiple user sessions? Would you have other suggestions if we want the batch sent to a user to stay, rather than rolling to the next available annotator? We can expose the settings for the timeout and that's probably a good idea – although, you typically want to at least have some level of work stealing enabled because otherwise, an annotator opening the app, looking around and then closing it again will lead to a batch not being annotated, which is typically not what you want. If you enable `PRODIGY_LOGGING=basic`, you should see a log message `FEED: re-adding open tasks to stream` whenever tasks are re-added for the next annotators. This should give you an idea whether this happens often in your scenario. --- _[View the full topic](https://support.prodi.gy/t/repeated-examples-in-multi-user-sessions/5235)._