# A NodeRed Challenge: Avoid the logging is filled with node results

**URL:** <https://discourse.nodered.org/t/a-nodered-challenge-avoid-the-logging-is-filled-with-node-results/95239>\
**Category:** General\
**Tags:** docker\
**Created:** [8 February 2025 12:10 UTC](https://discourse.nodered.org/t/a-nodered-challenge-avoid-the-logging-is-filled-with-node-results/95239 "2025-02-08T12:10:50Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [9 February 2025 20:29 UTC](https://discourse.nodered.org/t/a-nodered-challenge-avoid-the-logging-is-filled-with-node-results/95239/18 "2025-02-09T20:29:21Z")

</div>

> [@Steve-Mcl](#):
>
> Partly too, to prevent folk saying "how do i know which schedule was triggered" (early versions did NOT have the "fan out" option). Later, as it evolved more & dynamic ops were added, that meant a unique name for the schedule was necessary - so in theory, now, topic could be left blank. Instead, what I did was, if you leave it blank it w

To avoid derailing further, I made a separate discussion here: [Simplify flow using cronplus](https://discourse.nodered.org/t/simplify-flow-using-cronplus/95265)

---

_[View the full topic](https://discourse.nodered.org/t/a-nodered-challenge-avoid-the-logging-is-filled-with-node-results/95239)._