# Why we just wake up one task when reset a queue

**URL:** <https://forums.freertos.org/t/why-we-just-wake-up-one-task-when-reset-a-queue/10617>\
**Category:** Kernel\
**Created:** [September 7, 2020, 9:48am UTC](https://forums.freertos.org/t/why-we-just-wake-up-one-task-when-reset-a-queue/10617 "2020-09-07T09:48:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maidoumaizo](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@maidoumaizo](https://forums.freertos.org/u/maidoumaizo)\
**Post date:** [September 7, 2020, 9:48am UTC](https://forums.freertos.org/t/why-we-just-wake-up-one-task-when-reset-a-queue/10617/1 "2020-09-07T09:48:08Z")

</div>

![image](https://d2v6vdsk2p900z.cloudfront.net/original/1X/ebba70b1ec72271ab94ae0a2d032c46e2bff08d2.png)  
In xQueueGenericReset function, when we reset an already exist queue, why we just wake up only one waiting send task through calling xTaskRemoveFromEventList function  
I mean xTaskRemoveFromEventList function just can wake top priority task in waiting send list

---

<div class="post-metadata">

**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\
**Post date:** [September 7, 2020, 4:29pm UTC](https://forums.freertos.org/t/why-we-just-wake-up-one-task-when-reset-a-queue/10617/2 "2020-09-07T16:29:11Z")

</div>

This this has been asked before and the conclusion was the code was correct, but I can’t find the post right now, as on the face of it it would seem you need to unblock all tasks waiting to write. I will check what tests there are for this scenario and add some if they are lacking.