# Task lost on "page refresh"

**URL:** <https://support.prodi.gy/t/task-lost-on-page-refresh/2871>\
**Category:** Uncategorized\
**Tags:** usage, solved, streams\
**Created:** [May 5, 2020, 1:52pm UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871 "2020-05-05T13:52:20Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![akshayklr057](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@akshayklr057](https://support.prodi.gy/u/akshayklr057)\
**Post date:** [May 5, 2020, 1:52pm UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/1 "2020-05-05T13:52:20Z")

</div>

Hi,

What I have observed is that the task gets lost once the page is refreshed.  
How to avoid this?

---

<div class="post-metadata">

**Author:** ![justindujardin](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/justindujardin/32/169_2.png) [@justindujardin](https://support.prodi.gy/u/justindujardin)\
**Post date:** [May 5, 2020, 4:27pm UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/2 "2020-05-05T16:27:55Z")

</div>

Hi @akshayklr057,

Have you tried setting "force\_stream\_order" in your recipe? When you set that value to true, the app will repeat the same question until you answer it, even if you "page refresh".

---

<div class="post-metadata">

**Author:** ![akshayklr057](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@akshayklr057](https://support.prodi.gy/u/akshayklr057)\
**Post date:** [May 6, 2020, 4:41am UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/3 "2020-05-06T04:41:34Z")

</div>

Where to set it and how to use it? I don't see any reference to it in documentation.

---

<div class="post-metadata">

**Author:** ![akshayklr057](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@akshayklr057](https://support.prodi.gy/u/akshayklr057)\
**Post date:** [May 6, 2020, 4:57am UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/4 "2020-05-06T04:57:14Z")

</div>

I have set the "force\_stream\_order":true in prodigy.json, but it is still not working.

---

<div class="post-metadata">

**Author:** ![justindujardin](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/justindujardin/32/169_2.png) [@justindujardin](https://support.prodi.gy/u/justindujardin)\
**Post date:** [May 6, 2020, 2:28pm UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/5 "2020-05-06T14:28:40Z")

</div>

@akshayklr057 that's strange, can you tell me more about your setup? I have a few questions to help us figure out what's wrong.

What version of prodigy are you using? "force\_stream\_order" was introduced recently in v1.9, so if you're using an old version it might not work.

Can you take a screenshot or video of the problem happening? Your description isn't quite enough to help figure out what exactly is happening.

Can you start prodigy with verbose logging and show me the logs from your console when it doesn't work? You can do it like:

```bash
PRODIGY_LOGGING=verbose prodigy your_args_here

```

> [@akshayklr057](#):
>
> Where to set it and how to use it? I don't see any reference to it in documentation.

You can set the value in `prodigy.json` file in the current working directory that you're running. Here's a minimal config that uses the forced stream order option:

```json
{
  "theme": "eighties",
  "force_stream_order": true
}

```

I applied the eighties theme so it's easy for you to tell that the new configuration has been applied correctly. _It's important to know that if you have a prodigy.json file in your user's home directory, it will take precedence over one that's in the current working directory._

---

<div class="post-metadata">

**Author:** ![akshayklr057](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@akshayklr057](https://support.prodi.gy/u/akshayklr057)\
**Post date:** [May 7, 2020, 6:02am UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/6 "2020-05-07T06:02:09Z")

</div>

My version is 1.8, I guess that't why setting force\_stream\_order doesn't work.  
Thank you for the quick responses.

---

<div class="post-metadata">

**Author:** ![Balaji123](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/balaji123/32/2382_2.png) [@Balaji123](https://support.prodi.gy/u/Balaji123)\
**Post date:** [September 2, 2021, 8:29am UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/7 "2021-09-02T08:29:02Z")

</div>

Is there anyway to fix this issue for version 1.8

---

<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:** [September 2, 2021, 9:50am UTC](https://support.prodi.gy/t/task-lost-on-page-refresh/2871/8 "2021-09-02T09:50:56Z")

</div>

The `force_stream_order` setting was only introduced in Prodigy v1.9. If you're on v1.8 and not able to upgrade, you could implement something similar yourself with a custom stream generator that keeps looping over the incoming examples, checks them against the already annotated hashes and keeps sending out examples until they're annotated. See this post for example code:

> [@Struggling to create a multiple choice image classification](https://support.prodi.gy/t/struggling-to-create-a-multiple-choice-image-classification/1345/2):
>
> Hi! The it and tID indices make your code a little difficult to follow – but it looks like you’ve already solved the image choice part? Each example should have one or more "options" and each option should have an ID and a text. That should be all you need to make it render as an image with multiple choice options. The other thing you’re trying to do is loop over the examples over and over again until every example is in the database. Maybe it helps to break this down into steps. Fundamentally,…
