# QueueReceive max timeout

**URL:** <https://forums.freertos.org/t/queuereceive-max-timeout/23833>\
**Category:** Kernel\
**Created:** [September 9, 2025, 2:52pm UTC](https://forums.freertos.org/t/queuereceive-max-timeout/23833 "2025-09-09T14:52:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ShogunCoder](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@ShogunCoder](https://forums.freertos.org/u/ShogunCoder)\
**Post date:** [September 9, 2025, 2:52pm UTC](https://forums.freertos.org/t/queuereceive-max-timeout/23833/1 "2025-09-09T14:52:43Z")

</div>

Greetings.

The online documentation for xQueueReceive ( Documentation/02-Kernel/04-API-references/06-Queues/09-xQueueReceive ) says:

“If INCLUDE\_vTaskSuspend is set to ‘1’ then specifying the block time as portMAX\_DELAY will cause the task to block indefinitely (without a timeout).”

But the queue.h documentation in my clone of FreeRTOS-Kernel from github makes of this. I checked both V11.1.0 and origin/main and neither mention that the function can block indefinitely.

Peeking into the code, I think the support to block indefinitely has been there a long time, so I’m wondering about the documentation discrepancy.

---

<div class="post-metadata">

**Author:** ![jefftenney](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/jefftenney/32/1314_2.png) [@jefftenney](https://forums.freertos.org/u/jefftenney)\
**Post date:** [September 9, 2025, 11:06pm UTC](https://forums.freertos.org/t/queuereceive-max-timeout/23833/2 "2025-09-09T23:06:10Z")

</div>

It’s an omission in the code comments. The entire FreeRTOS API is pretty consistent about the behavior of portMAX\_DELAY as the xTicksToWait parameter. With `INCLUDE_vTaskSuspend`set to 1, the blocking has no timeout.