# Knowing when a node is done - new node API

**URL:** https://discourse.nodered.org/t/knowing-when-a-node-is-done-new-node-api/15737
**Category:** News
**Created:** [20 September 2019 23:12 UTC](https://discourse.nodered.org/t/knowing-when-a-node-is-done-new-node-api/15737 "2019-09-20T23:12:49Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [26 September 2019 09:23 UTC](https://discourse.nodered.org/t/knowing-when-a-node-is-done-new-node-api/15737/9 "2019-09-26T09:23:54Z")

</div>

@Hypnos thanks for reporting. Yes, you've found a problem with the recommended approach for migrating to the new api whilst keeping it backward compatible. I'm now curious as to why I didn't spot that in my testing.

The proper workaround is:

```auto
send = send || function() { node.send.apply(node,arguments) };

```

---

_[View the full topic](https://discourse.nodered.org/t/knowing-when-a-node-is-done-new-node-api/15737)._