# A flow has been disabled, because the Flow executed too many times **URL:** \ **Category:** Flows\ **Created:** [June 9, 2023, 8:49pm UTC](https://community.homey.app/t/a-flow-has-been-disabled-because-the-flow-executed-too-many-times/82036 "2023-06-09T20:49:04Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [June 12, 2023, 3:02am UTC](https://community.homey.app/t/a-flow-has-been-disabled-because-the-flow-executed-too-many-times/82036/5 "2023-06-12T03:02:02Z")
It’s an odd phenomenon I can tell. I’d like to suggest to start reading this post (from Athom tech @Jero Jeroen), and the posts below it > [@\[Timeline\] Flow disabled because it runs 60 times](https://community.homey.app/t/timeline-flow-disabled-because-it-runs-60-times/66238/25): > > It means the code thats runs the Flow did not exit properly. The code looks something like this: count++; try { const result = await this.run(args); return result; } catch (error) { throw error; } finally { // This block always executes. count--; } This can be triggered easily if you have a Flow that triggers every second that starts a delay for 120 seconds for example. On the 61th time the previous executions are not done yet so to prevent this ‘leak’ going on forever we disable the… . An idea for now: try to split your Adv. flow to 4 separate Adv flows to see it changes anything. I also want to suggest to [inform the app creator](https://github.com/DPANET/PrayersHomeySDK3/issues) about this. --- _[View the full topic](https://community.homey.app/t/a-flow-has-been-disabled-because-the-flow-executed-too-many-times/82036)._