# Stop Condition When It's Not Valid Any Longer

**URL:** <https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824>\
**Category:** Flows\
**Created:** [May 20, 2025, 9:43pm UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824 "2025-05-20T21:43:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 20, 2025, 10:15pm UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/2 "2025-05-20T22:15:22Z")

</div>

> [@Henric\_Waller](#):
>
> DELAY

Don’t use the built in delay for delays of more than a few seconds. Another ~~flaw~~ BUG when you use it for delays of (an) hour(s): it _does not survive a Homey reboot:_ you then can end up with unfinished flows without warnings whatsoever;  
And, as you’ve discovered: the delay isn’t interactive.

My preferred timer app is [Chronograph](https://community.homey.app/t/18214);  
It can start & continue a timer, start and replace a timer (reset & start again), pause and stop a timer. And it survives a Homey reboot.

This trigger card by [Device  
Capabilities](https://community.homey.app/t/43287) is way more flexible compared to the built-in ones:

 ![1000043063](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/5/a59d464257f9b9826c9b70e392f53c6d3397c988.jpeg)

 ![1000049036](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/3/0394a020d82552e413636586e18d6bfe7fd084fc.jpeg)

---

_[View the full topic](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824)._