# Advanced flows debugging

**URL:** <https://community.homey.app/t/advanced-flows-debugging/73120>\
**Category:** Ideas & Suggestions\
**Created:** [December 5, 2022, 10:54am UTC](https://community.homey.app/t/advanced-flows-debugging/73120 "2022-12-05T10:54:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mackelito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mackelito/32/8243_2.png) [@Mackelito](https://community.homey.app/u/Mackelito)\
**Post date:** [December 5, 2022, 10:54am UTC](https://community.homey.app/t/advanced-flows-debugging/73120/1 "2022-12-05T10:54:00Z")

</div>

Hey!  
I really like the advanced flows but it’s quite hard to figure out problems… if I have done a logical error then it might be really hard to backtrace and debug the problem…

I would like to be able to see triggered flows and to be able to follow exactly what happens.

---

<div class="post-metadata">

**Author:** ![Philip\_Montgomery](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philip_montgomery/32/12434_2.png) [@Philip\_Montgomery](https://community.homey.app/u/Philip_Montgomery)\
**Post date:** [December 5, 2022, 9:16pm UTC](https://community.homey.app/t/advanced-flows-debugging/73120/2 "2022-12-05T21:16:22Z")

</div>

You can, there is a test button that allows you to “watch” the process

---

<div class="post-metadata">

**Author:** ![Mackelito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mackelito/32/8243_2.png) [@Mackelito](https://community.homey.app/u/Mackelito)\
**Post date:** [December 5, 2022, 10:25pm UTC](https://community.homey.app/t/advanced-flows-debugging/73120/3 "2022-12-05T22:25:14Z")

</div>

Sure… but that is when creating/editing the flow… when you have more advanced flows that are depended on other factors like weather, presence or other data then you will only test for the dataset at that point in time… later on with other data that you might not have control over then it might fail… and there should be a way to backtrack failed runs of flows…

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [December 6, 2022, 12:05am UTC](https://community.homey.app/t/advanced-flows-debugging/73120/4 "2022-12-06T00:05:48Z")

</div>

The app Papertrials could add a log card to each and every ‘Then’ and ‘Then Else’ flow part of standard flows.  
There might be a chance this is becoming available for A.flows as well. Until that moment, I add a log card to each and every ‘output’ of a flow. The time spent with that, is nothing compared to the time I spend troubleshooting.  
It is a bit of weird there is no build-in ‘log’ thing of any kind, only the OnOff states of devices can reveal stuff.

---

<div class="post-metadata">

**Author:** ![Mackelito](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mackelito/32/8243_2.png) [@Mackelito](https://community.homey.app/u/Mackelito)\
**Post date:** [December 6, 2022, 1:29pm UTC](https://community.homey.app/t/advanced-flows-debugging/73120/5 "2022-12-06T13:29:24Z")

</div>

I have tried papertrail and it can help… but most likely not be enough in most cases…