# Find flow that isn't working

**URL:** <https://community.homey.app/t/find-flow-that-isnt-working/45344>\
**Category:** Ideas & Suggestions\
**Created:** [March 28, 2021, 8:06am UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344 "2021-03-28T08:06:45Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 8:06am UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/1 "2021-03-28T08:06:45Z")

</div>

Sometimes when a device is offline or I need to re-add the device some of the flows don’t work. But after add the device again I’ve to look which flow isn’t working annymore, because I’m using allot of folders. (in the web app)  
Is there a way to find it really easy, or its a thing that should be add to the web app.

 ![Schermafbeelding 2021-03-28 om 09.59.08](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3fcbd3d7c93f0f1b6f357f9465af653d3ed525f6.png)

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [March 28, 2021, 3:05pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/2 "2021-03-28T15:05:54Z")

</div>

Perhaps not really what you’re looking for but in the mobile app you can see quite easily see which Flow is broken (exclamation mark on the right of the flow name).  
Do not select a folder, then all the flows are visible and easy to scroll through.

 ![SmartSelect_20210328-170718_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/6/060ebd3d3c5cd67986787e9876d201c3744dc18b.jpeg)

I suppose it has to be implemented in the web app. Would be a nice feature!

---

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 3:22pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/3 "2021-03-28T15:22:58Z")

</div>

Yes that’s what I’m already use to search, but for changing flows it’s faster on the web app. I’ve now 300+ flows so it will take allot of time to find everything.

A feature that’s saying with flows don’t work is in mine opinion easier to find an incorrect flow.  
Or to have the possibility to make a flow (for notification) when a flow is incorrect.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [March 28, 2021, 3:42pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/4 "2021-03-28T15:42:51Z")

</div>

> [@Developer Web API Playground - Notes of geeky oneliners](https://community.homey.app/t/developer-web-api-playground-notes-of-geeky-oneliners/24392/1):
>
> ```auto
> // Or Get broken flows
> // Run and only the broken flows are returned ;-)
> Homey.flow.getFlows().then(f => Object.values(f).reduce((r,b)=> Object.assign(r, b.broken ? {[b.name]:b.broken} : ''), {}) );
> 
> ```

This?

---

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 3:43pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/5 "2021-03-28T15:43:51Z")

</div>

Thanks I think this is what I’m looking for. I’m going to try it.

---

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 4:32pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/6 "2021-03-28T16:32:18Z")

</div>

I think this is the solution. At the moment I’ve no incorrect flows, but when I have I’m going to check it.

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [March 28, 2021, 5:14pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/7 "2021-03-28T17:14:14Z")

</div>

> [@Dijker](#):
>
> This?

Great @Dijker ! Very helpful!

Can this be turned into a Homeyscript as well, with notification on the timeline (or phone)? That way we can schedule this by a flow…

---

<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:** [March 28, 2021, 6:22pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/8 "2021-03-28T18:22:56Z")

</div>

Well, create virtual device type switch, create test flow, VD switch is trigger, do something as action. Save the flow, delete the virtual device from your devices list  
Now this flow should come up when running the script.

It is not 100% failsafe though, a removed variabele doesn’t mark a flow as broken (yet)

---

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 6:48pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/9 "2021-03-28T18:48:55Z")

</div>

Thanks! Didn’t think about it

---

<div class="post-metadata">

**Author:** ![Arjan-21](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan-21/32/27181_2.png) [@Arjan-21](https://community.homey.app/u/Arjan-21)\
**Post date:** [March 28, 2021, 6:52pm UTC](https://community.homey.app/t/find-flow-that-isnt-working/45344/10 "2021-03-28T18:52:56Z")

</div>

> [@Developer Web API Playground - Notes of geeky oneliners](https://community.homey.app/t/developer-web-api-playground-notes-of-geeky-oneliners/24392/1):
>
> ```auto
> // Or Get broken flows
> // Run and only the broken flows are returned ;-)
> Homey.flow.getFlows().then(f => Object.values(f).reduce((r,b)=> Object.assign(r, b.broken ? {[b.name]:b.broken} : ''), {}) );
> 
> ```

This works really great!!

 ![Schermafbeelding 2021-03-28 om 20.52.10](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/7/b7fd476439563e79cf8e1a8e59c0c5286def5a46.png)
