# Link Call without timeout

**URL:** <https://discourse.nodered.org/t/link-call-without-timeout/100226>\
**Category:** Feature Requests\
**Created:** [23 January 2026 16:22 UTC](https://discourse.nodered.org/t/link-call-without-timeout/100226 "2026-01-23T16:22:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [23 January 2026 16:22 UTC](https://discourse.nodered.org/t/link-call-without-timeout/100226/1 "2026-01-23T16:22:11Z")

</div>

Per this post -

> [@Link call set to dynamic - can there be other link nodes in the flow?](https://discourse.nodered.org/t/link-call-set-to-dynamic-can-there-be-other-link-nodes-in-the-flow/97438/19):
>
> I've spotted a problem with disabling the timeout; the node tracks each message it sends so that when a response comes back it can send the response in the context of the message that triggered it. If we disable the timeout, then that state will still accumulate in the node, never being cleared - leaking memory. I've come to the conclusion that: Link Call should not allow the timeout to be disabled - it always expects a response The Link Out node should have a dynamic mode added to it to sat…

Can the above be implemented to increase the usefulness of link call nodes.

I think it would be a nice additional option.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [24 March 2026 17:42 UTC](https://discourse.nodered.org/t/link-call-without-timeout/100226/3 "2026-03-24T17:42:23Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.