# Automatically disabled flows in 2.05

**URL:** <https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518>\
**Category:** Questions & Help\
**Created:** [March 13, 2019, 8:02am UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518 "2019-03-13T08:02:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![maja2020](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maja2020/32/3549_2.png) [@maja2020](https://community.homey.app/u/maja2020)\
**Post date:** [March 13, 2019, 8:02am UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/1 "2019-03-13T08:02:40Z")

</div>

Last night v2.05 install disabled about 15 flows that start on a 2 min interval or less.  
These flows are very simple variable value calculations based on sensor values.

Does anyone know what makes homey decide a flow should be automatically disabled?

---

<div class="post-metadata">

**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\
**Post date:** [March 13, 2019, 8:05am UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/2 "2019-03-13T08:05:04Z")

</div>

If the flow is called more than 10x a second or more 120x a minute and your flow will be disabled.

---

<div class="post-metadata">

**Author:** ![maja2020](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maja2020/32/3549_2.png) [@maja2020](https://community.homey.app/u/maja2020)\
**Post date:** [March 13, 2019, 9:46am UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/3 "2019-03-13T09:46:34Z")

</div>

The flows were disabled on homey startup after the update installed. I re-enabled them and it works fine (as it did for 1,5 years since I build them).

These flows all start on a date-time card each minute or each 2 minutes.  
I can see the calculations in a flow execute within a second (better logic records the last change time stamp of a variable).  
I can also see that different one minute flows start after each other with one second in between.

Nothing that looks like 10x a second…  
I guess that Homey allows the flows to run, this is a glitch of the update or restart process.

---

<div class="post-metadata">

**Author:** ![bvdbos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bvdbos/32/2352_2.png) [@bvdbos](https://community.homey.app/u/bvdbos)\
**Post date:** [March 13, 2019, 1:22pm UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/4 "2019-03-13T13:22:55Z")

</div>

There is no 2.0.5 yet? Only an experimental release with firmware which may have bugs…

---

<div class="post-metadata">

**Author:** ![JonE](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@JonE](https://community.homey.app/u/JonE)\
**Post date:** [June 20, 2019, 1:53pm UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/5 "2019-06-20T13:53:50Z")

</div>

this is still happening for me. Anyone knows how to disable this very annoying behaviour? I’m on 2.2.0rc7. Hope I can stop this…

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [June 20, 2019, 2:20pm UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/6 "2019-06-20T14:20:31Z")

</div>

[Duplicate topic](https://community.homey.app/t/how-to-stop-flows-disabled-functionaliteit-in-v2-05-rc2/10157) so closed.

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [June 20, 2019, 2:20pm UTC](https://community.homey.app/t/automatically-disabled-flows-in-2-05/10518/7 "2019-06-20T14:20:36Z")

</div>

Closed on June 20, 2019, 2:20pm UTC


