# "Yield Task" not yielding some tasks **URL:** \ **Category:** Uncategorized\ **Tags:** usage\ **Created:** [March 19, 2019, 9:36pm UTC](https://support.prodi.gy/t/yield-task-not-yielding-some-tasks/1319 "2019-03-19T21:36:26Z")\ **Posts on this page:** 1\ **Showing post:** 7
**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 21, 2019, 9:31am UTC](https://support.prodi.gy/t/yield-task-not-yielding-some-tasks/1319/7 "2019-03-21T09:31:38Z")
> [@ameliatqy](#): > > But I am not sure about the case in which the Prodigy instance is already running and the ignored annotations are generated during the session - I’ll let you know when I test that scenario out. Yes, that'd definitely be interesting! Also, if the existing answer _is_ the cause here, one quick fix should be to overwriteit /remove it from the task dict before sending it out? And if not, that'd also be interesting, since it means something else would be going on, if I understand this correctly? > [@ameliatqy](#): > > I am still using the old version of Prodigy for this (Prodigy 1.6 - Prodigy 1.7 returns JWT: caller token did not validate when I try to start it up. Btw, I think we have a fix for that – see here: > [@Super basic authentication](https://support.prodi.gy/t/super-basic-authentication/233/8): > > @koAlech Hurray for authenticating users, and welcome! We’ve begun integrating more full-featured authentication for Prodigy Scale, and the snippet you used conflicts with that code. A workaround is to remove the occurrences of the string , requires=conditional\_api\_token from app.py. This will remove your ability to use the PRODIGY\_JWT\_\* environment variables, but if you want to use basic auth, that should be no problem. edit: there’s a better fix below --- _[View the full topic](https://support.prodi.gy/t/yield-task-not-yielding-some-tasks/1319)._