# How to force fixed point (delaying execution) after random triggering **URL:** \ **Category:** Questions & Help\ **Tags:** flow, homey-pro\ **Created:** [May 21, 2025, 4:51pm UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862 "2025-05-21T16:51:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Eko\_taas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eko_taas/32/74256_2.png) [@Eko\_taas](https://community.homey.app/u/Eko_taas)\ **Post date:** [May 21, 2025, 4:51pm UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/1 "2025-05-21T16:51:35Z")
I want to delay some flow triggering to exact minutes, so tested with this flow ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/4/84e9b97d2280220a6deb487a6f2865fb23a4acd5.png), where: - “Transition” rep. steps (every 3min) I would allow to finally execute flow, if triggered (xx:00, xx:03 etc. - Every 3 min just acting like test-trigger - fixed delay used to test if any effect (I know using “and” looks strange on triggering, but) based on test even same time 2 triggers not creating message. Non of 3 coming thru… only basic message OK… Reason for trial: cannot find dynamic wait-card and testing,testing Better ideas how to make same functionality? ---
**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\ **Post date:** [May 21, 2025, 8:08pm UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/2 "2025-05-21T20:08:36Z")
For each ALL-card you have two triggers. This will never work. ---
**Author:** ![Eko\_taas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eko_taas/32/74256_2.png) [@Eko\_taas](https://community.homey.app/u/Eko_taas)\ **Post date:** [May 22, 2025, 5:42am UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/3 "2025-05-22T05:42:12Z")
Yes, thus looking for better ideas ---
**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\ **Post date:** [May 22, 2025, 8:50am UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/4 "2025-05-22T08:50:37Z")
If I understand your problem correctly you want a flow that triggers at 12:01 waits till 12:03 before continuing?. I would create a YES/NO variable ‘all conditions are met’ and set this to YES when the flow triggers and conditions are true. WHEN transition reaches a step AND ‘all conditions are met’ is YES THEN set ‘al conditions are met’ to NO proceed with the rest of the flow ---
**Author:** ![Eko\_taas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eko_taas/32/74256_2.png) [@Eko\_taas](https://community.homey.app/u/Eko_taas)\ **Post date:** [May 26, 2025, 1:44pm UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/5 "2025-05-26T13:44:54Z")
> For each ALL-card you have two triggers. This will never work. After many delay-cards etc. can confirm was not able to find “cheat”… > YES/NO variable ‘all conditions are met’ Thank you for idea - unfortunately I have decided long back to avoid all variables on my flows (long story)… After further testing ended up with bit (too/) more complicated solution at the end: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/8/a84c6297937c3b2df240683afc07474f97b0c8a5.png) 15min timer is already existing on my Homey set-up for other purposes, so used that on my testing: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/8/58cf57e07f0808c5ead2fde84ca4bac2e983bb2c.png) Seems to do exact what I wanted… each flow executes only every 3 min - even if triggered twice within 3min (and easy to adjust as/if needed): ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/5/058137691d1defb3024d2347b8a22586ac1c4028.png) ---
**Author:** ![Eko\_taas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eko_taas/32/74256_2.png) [@Eko\_taas](https://community.homey.app/u/Eko_taas)\ **Post date:** [June 9, 2025, 10:30am UTC](https://community.homey.app/t/how-to-force-fixed-point-delaying-execution-after-random-triggering/136862/6 "2025-06-09T10:30:00Z")
(Update just in case someone is still interested / has similar ambition of “simplification” ) Finally landed with very simple 😬 but greatly stabilizing my Homey (and its HomeyScript challenges) by creating “full re-usable” sub-flow: (I am sure not fully optimal, but seems to address all **my own needs** perfectly) Part 1: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/0/d0f9b359b778971c6bfafdcaaf7ca6b8ba4bd8db.png) Part 2: (cont., error reporting for testing left outside as zero errors in last 2 days 😇) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/65191e0a311c0f0f181a17f47d5713b7fd57eefa.png) Now all my “randomly” triggered (heavier) flows can be timed to exact slot on desired cycle length (using 5min / 15min / 60min / 6hUTC / 24hUTC) while improved my main flows greatly to be more simple than before (had many if/delay etc. cards) while sticking on my zero-variants policy 🙂 Below example of main flow: each main task will only run if : - triggered randomly (by any to all triggers) - forced call (w/o parameters, resetting also earlier triggers) Random triggering results execution: - at **3min** cycle + **1** min/ **2** min - … but never before every **15** min + **2,9** min and latest +15min- **5,2** min (protected time) - only once per cycle independent at what time / how many times it has been was trigged. (showing 2 separately controlled “zones”, separate actions for each with one common trigger) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/8/b87294cea9d5a8f260024972ad4341031b9278ed.png) Sidenotes: - here main-flow is calculating optimal heating expectation only, while final heater decision on separate flow not to change mind too often 🙂 - Tested also that “Timer id finished” triggering only once (to be on safe side)…