# showing no task available even data not yet completely annotated **URL:** \ **Category:** Uncategorized\ **Tags:** usage\ **Created:** [March 19, 2019, 7:12am UTC](https://support.prodi.gy/t/showing-no-task-available-even-data-not-yet-completely-annotated/1312 "2019-03-19T07:12:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [March 19, 2019, 8:50am UTC](https://support.prodi.gy/t/showing-no-task-available-even-data-not-yet-completely-annotated/1312/2 "2019-03-19T08:50:44Z")
Hi! Which recipe are you running? If you're running an active learning-powered recipe like `ner.teach` or `textcat.teach`, this is expected – remember that you're annotating the _most relevant examples_ here, so Prodigy will score them and skip some examples in favour of others. In `ner.teach`, you'll also be seeing lots of different analyses of individual examples. If your goal is to just annotate every single example in your stream, you probably want to be using a manual recipe. You can find more details in this thread: > [@"No tasks available" even though there's plenty of samples left](https://support.prodi.gy/t/no-tasks-available-even-though-theres-plenty-of-samples-left/51/2): > > Thanks for the report! Just tested it with your example data and came across the same behaviour. There weren’t any errors either, so I think what might be happening here is the following: textcat.teach scores the stream and tries to only show you the most relevant tasks. Since there are only 100 examples, the “most relevant” selection seems to be only about 10-20%, which means the stream is exhausted after 10-20 examples. This is probably unideal, and we’ll think about the best way to handle t… --- _[View the full topic](https://support.prodi.gy/t/showing-no-task-available-even-data-not-yet-completely-annotated/1312)._