# "No tasks available" on page refresh

**URL:** <https://support.prodi.gy/t/no-tasks-available-on-page-refresh/155>\
**Category:** Uncategorized\
**Tags:** usage, custom, solved\
**Created:** [December 23, 2017, 8:23am UTC](https://support.prodi.gy/t/no-tasks-available-on-page-refresh/155 "2017-12-23T08:23:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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:** [December 27, 2018, 7:26pm UTC](https://support.prodi.gy/t/no-tasks-available-on-page-refresh/155/4 "2018-12-27T19:26:38Z")

</div>

Ah yes – sorry, I forgot to actually add logic to refresh the stream generator.

> [@MajidD4t1qbit](#):
>
> Now, if I change the snippet to re-create the stream when it’s fully traversed as follows, it does not stop even after all of the images are traversed.

At any time in your loop, you can `break` – but you have to decide when the stream is actually "done". When you're sending out the new questions, you don't always know what answers were "lost" and what answers are still being answered. Maybe the annotator is just taking a while and still has the questions in the queue – in that case, you might not want to send them out again immediately.

A very basic solution would be to check the hashes of the incoming examples against the hashes already present in the current dataset and break if all hashes are covered. You might find this thread useful, which explains a lot of this in more detail and has some examples:

> [@ordered tasks on "mark" receipe](https://support.prodi.gy/t/ordered-tasks-on-mark-receipe/1033/2):
>
> The --memorize flag will exclude examples that are already in the dataset. By “different annotators running on different machines”, do you mean separate Python processes? Because if you run separate processes with the same input data and different target dataset names in the database, the questions should be asked in the exact same order, as they come in. The only thing that’s important to consider is the reloading: If you refresh the browser, Prodigy will make a call to /get\_questions, which…

---

_[View the full topic](https://support.prodi.gy/t/no-tasks-available-on-page-refresh/155)._
