# DEBUG window suggestion

**URL:** <https://discourse.nodered.org/t/debug-window-suggestion/87383>\
**Category:** Feature Requests\
**Created:** [21 April 2024 11:16 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383 "2024-04-21T11:16:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [21 April 2024 13:51 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/5 "2024-04-21T13:51:19Z")

</div>

I don't know if there are plans to improve debug nodes.

In the meantime, here is a [suggested approach](https://discourse.nodered.org/t/output-to-debug-window-disappears-too-fast/86316/12)

It's not the slightest bit elegant but has some advantages

- You replace all debug nodes with a simple link to a central debug flow (or sublflow?).
- You can restrict those messages which get displayed according to msg.topic
- You can allow or prohibit any where msg.topic is not included in the filter list.

---

_[View the full topic](https://discourse.nodered.org/t/debug-window-suggestion/87383)._
