# Add a Debugger Please

**URL:** <https://community.tulip.co/t/add-a-debugger-please/6329>\
**Category:** Product Suggestions\
**Created:** [September 8, 2022, 8:03pm UTC](https://community.tulip.co/t/add-a-debugger-please/6329 "2022-09-08T20:03:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ktoole](https://avatars.discourse-cdn.com/v4/letter/k/b9bd4f/32.png) [@ktoole](https://community.tulip.co/u/ktoole)\
**Post date:** [September 8, 2022, 8:03pm UTC](https://community.tulip.co/t/add-a-debugger-please/6329/1 "2022-09-08T20:03:41Z")

</div>

It would be very helpful if there was a traditional debugger like a VBA terminal has. One that steps through your triggers line by line in the test environment. This would let us test where a misfire is on the line level of a trigger.

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [September 9, 2022, 11:42am UTC](https://community.tulip.co/t/add-a-debugger-please/6329/2 "2022-09-09T11:42:55Z")

</div>

Hey @ktoole -

Welcome to Community!

Thanks for this idea, I completely agree that this would streamline the app-building process. There is work in flight right now around a number of big improvements to triggers including a more visual view of trigger _flows_. The engineering work is in-flight right now. At least initially the debugging with be more similar to the debugging of a connector (with the test button), but will be a gigantic step towards action-by-action understanding of your application logic.

Your post ignited a really good conversation internally on a number of ways Dev Mode could be improved. A step through mode is one of 2 or 3 things that there is agreement we need.

Keep the good ideas coming!  
Pete