# \[FeatureRequest\] Run flow once and then it deletes itself? **URL:** \ **Category:** Ideas & Suggestions\ **Tags:** featurerequest\ **Created:** [January 1, 2025, 3:29pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119 "2025-01-01T15:29:20Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 1, 2025, 3:29pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/1 "2025-01-01T15:29:20Z")
Hey Homeys! Is there a way to create a flow to run only once in the future and then it deletes itself? I have found myself having this need several times but has not been able to figure out how create it, if it’s even possible. Let me give you an example from today: I have a mower bot that is in winter hibernation at the moment. It’s stored in its charging station tucked away under a staircase going down to your basement. I have the charging station connected to mains power through a Zigbee plug and have set up a flow that turns on the plug for two hours once a month for top up charging of the battery. This works fine until it doesn’t. My Homey is not 100 % stable, so sometimes different coms protocol fails or Homey goes offline. If this happens when the flow is supposed to be started it obviously won’t. This happened today. For some reason the Zigbee protocol was malfunctioning and the charging did not start. I hade to restart Homey for it to start functioning normally again. In this scenario I would like to be able to create a flow that when started turns the Zigbee plug on and after two hours turns it off again which is no problem of course. But now I have a flow that I don’t need anymore and I have to remember to delete it manually. Since the whole idea with automation is to minimise manual input I would love to be able to add a function in the flow that deletes itself when all actions have been taken. Is this possible somehow or is this something that I should put in the “Idea and suggestions” section? ---
**Author:** ![RoyWissenburg](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@RoyWissenburg](https://community.homey.app/u/RoyWissenburg)\ **Post date:** [January 1, 2025, 3:44pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/2 "2025-01-01T15:44:14Z")
read it a few times, and really dont get it. Why you want a flow get delete after the flow is done? because then you need to make a new flow for the next time. Or iam missing something. ---
**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\ **Post date:** [January 1, 2025, 4:23pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/3 "2025-01-01T16:23:27Z")
> [@Paxman](#): > > I would like to be able to create a flow that when started turns the Zigbee plug on and after two hours turns it off again Looks like you already have that flow? (Just triggered by a different WHEN. you can manually trigger this flow to run… > [@Paxman](#): > > have set up a flow that turns on the plug for two hours once a month for top up charging of the battery You can also trigger this flow automatically when homey restarts ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 1, 2025, 4:54pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/4 "2025-01-01T16:54:29Z")
> [@RoyWissenburg](#): > > read it a few times, and really dont get it. Why you want a flow get delete after the flow is done? because then you need to make a new flow for the next time. > > Or iam missing something. Yes. There are situations when I want to create a flow that will only be used once. The situation I described in my first post was just an example. > [@FKey](#): > > Looks like you already have that flow? (Just triggered by a different WHEN. > you can manually trigger this flow to run… See my answer above. > [@FKey](#): > > You can also trigger this flow automatically when homey restarts This I know…but that would not be applicable to what I’m asking for. ---
**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:** [January 1, 2025, 6:24pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/5 "2025-01-01T18:24:44Z")
Imho you’re trying to workaround a occasional hickup Here’s a script to inform you of devices which didn’t report anything the last X hours > [@A script to check sensor last update](https://community.homey.app/t/a-script-to-check-sensor-last-update/63142/39): > > As there is for some time options to see Lastseen timestamp for Zigbee devices, here is the script for Zigbee devices only, which might be more accurate for Zigbee devices. Thanks @Caseda for your overview script wink Version 0.3 - updated for HomeyScript v. 3.5.1 Version 0.3b - fixed for THEN card (returning TEXT value), primary use-better use is for AND card though Version 0.4 - added option to filter out routers and/or end devices // Version 0.4 // Script checks LastSeen property of Zig… It depends on the brand & model of the smart plug though. If it reports power, or voltage, or signal strength and such, you’re good. About the _why_ of the zigbee issue, there can be several causes _you_ can prevent: > [@Advanced Zigbee Troubleshooting on Homey](https://community.homey.app/t/advanced-zigbee-troubleshooting-on-homey/115930): > > If you’re experiencing issues with your Zigbee network on Homey, here are advanced troubleshooting steps to help optimize performance and stability, especially in more complex environments: Power Supply Integrity A stable power supply is critical for Homey’s performance. An underpowered adapter can lead to instability in the Zigbee network. Always ensure you’re using a reliable adapter providing at least 2A. Power fluctuations can cause disconnections or communication failures, especially un… ---
**Author:** ![JohanP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johanp/32/119002_2.png) [@JohanP](https://community.homey.app/u/JohanP)\ **Post date:** [January 1, 2025, 6:42pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/6 "2025-01-01T18:42:52Z")
> [@Paxman](#): > > Since the whole idea with automation is to minimise manual input Thats the opposite of using a flow once… ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 2, 2025, 12:27am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/7 "2025-01-02T00:27:26Z")
Thank you guys for your creative posts…however, it’s really interesting on forums like this that you can ask a simple question and get a whole lot of answers to other things. 😄 > [@Peter\_Kawa](#): > > Imho you’re trying to workaround a occasional hickup Well, no. The hiccup was an example. As I wrote in my first post I have encountered other instances where the function I’m after would have been good to have. > [@JohanP](#): > > Thats the opposite of using a flow once… No, it’s not. In my example there was a fault in the automation and I wanted to run the missed action. Sure, I could have made a flow that turned the charging on for two hours and the turned it off again, but then I would have had to remember to **manually** delete the flow after the two hours have passed. That is opposite of automation. It’s not hard to imagine a situation where you write a flow with a lot of commands that you only need to run once due to a specific need you have just then. It could even be over several days or even months/years for that matter. When the scenario is over you will never need it again. So again, thank you for your creative solutions to my example…that one has now passed (the mower is all charged up). However the thread question still remains: is there a way to get a flow to self delete when it has done its thing? ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [January 2, 2025, 7:02am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/8 "2025-01-02T07:02:24Z")
> [@Paxman](#): > > However the thread question still remains: is there a way to get a flow to self delete when it has done its thing? No ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [January 2, 2025, 8:06am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/9 "2025-01-02T08:06:42Z")
What stops you from running your existing permanent flow manually? Are you using advanced flows or the simple flows? You can add other trigger “When” cards to your existing flow. For example the with advanced flows you can add the “Start” option to your flow ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/ed12a5ea993a02f2b7faa687ca4a5766782a87ec.png) ---
**Author:** ![RoyWissenburg](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@RoyWissenburg](https://community.homey.app/u/RoyWissenburg)\ **Post date:** [January 2, 2025, 8:40am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/10 "2025-01-02T08:40:08Z")
> [@Paxman](#): > > Thank you guys for your creative posts…however, it’s really interesting on forums like this that you can ask a simple question and get a whole lot of answers to other things. 😄 Wel, people where thinking along with you by giving posible solutions or easy workarounds. Onestly stil dont get your point, for what your trying to do / what you want, thats fine 😀 To the point, the answer yes/no is already given. ---
**Author:** ![JohanP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johanp/32/119002_2.png) [@JohanP](https://community.homey.app/u/JohanP)\ **Post date:** [January 2, 2025, 8:58am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/11 "2025-01-02T08:58:55Z")
> [@Paxman](#): > > > [@JohanP](#): > > > > Thats the opposite of using a flow once… > > No, it’s not. Yes it is 😉 Automation is not having to do repetitive tasks manually, a flow for a one-time event is not automation. If it happens more often you either need to implement a more fault-tolerant flow or create a flow that wil remedy the fault… ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 2, 2025, 10:51am UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/12 "2025-01-02T10:51:18Z")
Since the answer to my question is “no” I will post a request for this feature in the correct category. 👍 😁 ---
**Author:** ![Yngve\_Nystrand](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yngve_nystrand/32/90873_2.png) [@Yngve\_Nystrand](https://community.homey.app/u/Yngve_Nystrand)\ **Post date:** [January 8, 2025, 3:06pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/13 "2025-01-08T15:06:43Z")
Hi, I had a similar need to run a flow only once, at a certain time of the day. In my case, I wanted to start charging my car at that time, but only once and not every day. So I solved it by letting the flow disable itself as the last action. And if you let it send you a notification before it disables itself, then you will be reminded to delete the flow, if that is what you want. ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 8, 2025, 3:19pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/14 "2025-01-08T15:19:14Z")
That’s a good workaround Yngve…but it’s still to manual for me… 😉 ---
**Author:** ![tlink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tlink/32/120666_2.png) [@tlink](https://community.homey.app/u/tlink)\ **Post date:** [January 8, 2025, 4:40pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/15 "2025-01-08T16:40:48Z")
Why don’t you trigger the flow using an alarm from the Mobile app? After reading your description, the unstable Homey connection can happen any time in the future again. So, why do you need to delete that flow and recreate it in the future with the next failure?? “One-time flows” might be an extreme edge case. It looks like your goal is more to have a tidy list of flows in the app. a) Create a folder for your one-time flows, and maybe use them as templates in the future b) Combine multiple flows of a single device in one advance flow Maybe, there’s flow/app that asks for a device and duration on launch and executes the on/off actions? ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 8, 2025, 4:50pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/16 "2025-01-08T16:50:28Z")
Please…the example I wrote in my first post was an **example**. It’s not the only instance that I have encountered when the need for a “one time only then delete”-flow has occurred. I don’t need help solving the issue with the missed charging of my robot, it is fully charged now (which I had to do manually) and waiting for it’s next top up charging scheduled in Homey. If there is a glitch that time too it’s no problem…it will probably be charged the next scheduled time. Yngve shows that the need for “one time only then delete”-flow is not unique for me (and I’m sure he and I are not the only ones), so why are you guys so against the suggestion for the function? If you don’t see the need for it…move along. ---
**Author:** ![Mike1233](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike1233/32/20991_2.png) [@Mike1233](https://community.homey.app/u/Mike1233)\ **Post date:** [January 8, 2025, 8:17pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/17 "2025-01-08T20:17:53Z")
@paxman I have also no idea how to remove a flow automaticly but what i do is. I have a folder in Homey called Eenmalig uitvoeren. In that folder i made for example a flow that sends every day a Whatsapp that i must feed the dog of my neigbour. And a flow that i should take every 8 hours my medication for 7 days. And once in a while i throw all the flows away without watching what i am deleting. That is my workflow for this problem. ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 8, 2025, 8:01pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/18 "2025-01-08T20:01:35Z")
Hey Homeys! A few times I have found myself needing to create a flow that will only be used once. I’ll refrain from giving any existing examples (since if I do some people will not be able to resist the urge to solve it in more or less creative ways that are workarounds for what I’m suggesting as a function). So I will try to give an hypothetical example. Let’s say that I never leave my house more than a couple of days in a row and my biggest hobby is to water my house plants. However, now I’m planning to go away on a two week trip. I rig a plant watering system with a little pump that I schedule to run for 5 seconds every other day during my absence. I would love to have a ”delete flow”-card that I can put in the flow for this watering schedule when it has run its course. WHEN ”date is” _day of my arrival home_ THEN ”Delete flow”. Launch and forget so to say. With this function the user can create flows for one time events and never have to remember to delete them when the event is over. I know that some of you that are reading this see no use of such a function, and that is fine. But please can I ask you not to express that opinion in this thread. Also, I’m sure that some of you have super great ways to fix the watering example I gave above…but please understand that I don’t need it solved since it’s hypothetical example (I hate my plants). I see the need for this ”delete flow”-card, and that is fine to…and since this is the suggestions and idea category everyone should be free to post suggestions and ideas without having to defend them to other members of the forum. If you think my idea is stupid please just move along and by all means feel free to laugh at me on your side of your screen. ---
**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:** [January 8, 2025, 9:53pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/20 "2025-01-08T21:53:01Z")
> [@Paxman](#): > > since if I do some people will not be able to resist the urge to solve it in more or less creative ways that are workarounds for what I’m suggesting as a function Well, I guess I am one of those people as you’ve read 🤣 I think everyone is just wired in a (slightly) different way. You seem to think everyone thinks the same way you do. You put it in a sort of kind way, but, to me, you say: “don’t bug me with your workarounds and ideas for different approaches”. I’d like to suggest for future questions: Please specify the kind of answer you like to see, in this case a boolean one, Y/N. Saves me, and you, some time and effort as well! Oh, and about: > [@Paxman](#): > > and since this is the suggestions and idea category everyone should be free to post suggestions and ideas NO, you asked a question or asked for help. #### Maybe here’s the cause of our misunderstanding: > ![1000041078](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/2/728b86b588d6ee85726f3acc6d279e20109354be.jpeg) Thanks and mycket glädje, tak. ---
**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\ **Post date:** [January 8, 2025, 10:33pm UTC](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119/21 "2025-01-08T22:33:16Z")
> [@Peter\_Kawa](#): > > NO, you asked a question or asked for help. But I did post it in Suggestions and ideas! For some reason it was moved back here which I think is wrong. In this thread I asked if this function existed and was told it was not. Therefore I started a new thread in Suggestions and ideas requesting the function. How can that be wrong? [Next page](https://community.homey.app/t/featurerequest-run-flow-once-and-then-it-deletes-itself/126119.md?page=2)