# 42. How to monitor outputs

**URL:** <https://community.triggre.com/t/42-how-to-monitor-outputs/600>\
**Category:** Weekend masterclass\
**Tags:** designer, outputs, flow-parts\
**Created:** [December 1, 2023, 8:39am UTC](https://community.triggre.com/t/42-how-to-monitor-outputs/600 "2023-12-01T08:39:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marta](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/marta/32/87_2.png) [@Marta](https://community.triggre.com/u/Marta)\
**Post date:** [December 1, 2023, 8:39am UTC](https://community.triggre.com/t/42-how-to-monitor-outputs/600/1 "2023-12-01T08:39:40Z")

</div>

In this new installment of the “Triggre Weekend Masterclass” series, Eddie is back to guide you through a crucial aspect of no-code development. Sometimes, an application’s logic is made of several interconnected Flow Parts, which makes troubleshooting quite challenging. With this trick, you’ll be able to effectively monitor the behavior and outputs of different Flow Parts.

[![](https://canada1.discourse-cdn.com/flex035/uploads/triggre/original/1X/0c2a6e29357808174e011ae9cf05af8e99fb6376.jpeg "Simplify troubleshooting with this trick to monitor outputs | Triggre Weekend Masterclass") ](https://www.youtube.com/watch?v=3KOAuGvTlUU)