# Message tracing in NR5

**URL:** <https://discourse.nodered.org/t/message-tracing-in-nr5/101278>\
**Category:** General\
**Tags:** node-red-5\
**Created:** [13 June 2026 15:40 UTC](https://discourse.nodered.org/t/message-tracing-in-nr5/101278 "2026-06-13T15:40:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [17 June 2026 08:54 UTC](https://discourse.nodered.org/t/message-tracing-in-nr5/101278/4 "2026-06-17T08:54:40Z")

</div>

> [@KristopherLeads](#):
>
> auto-trigger in place to turn off the trace

![Screenshot 2026-06-17 at 10.33.27](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/f/0f33b2cf5bd416be7e4273611fbc19b9b84306da.png)

Fyi, with [0.14.0](https://flows.nodered.org/node/@gregoriusrippenstein/node-red-contrib-introspection) I've now added a fail-safe that deactivates the tracing if \>100 msg per second are being received. That is configured for both clamp more and select-and-trace mode. The limit can be overridden in the editor, how to do this is described in the readme.

---

_[View the full topic](https://discourse.nodered.org/t/message-tracing-in-nr5/101278)._