# Timeline RATE-LIMIT without error notification

**URL:** <https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046>\
**Category:** Ideas & Suggestions\
**Tags:** flow, advancedflow, messaging\
**Created:** [October 7, 2022, 4:36pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046 "2022-10-07T16:36:29Z")\
**Posts on this page:** 7\
**Page:** 1

<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:** [October 7, 2022, 4:36pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/1 "2022-10-07T16:36:29Z")

</div>

Hi all,

Fact: The timeline can get rate-limited when sending too many notifications from flows, within a certain time frame.

1. Why isn’t an error message sent or present somewhere?  
Say a push message, or a timeline message (while only the flow category seems to be rate-limited).  
Now I only discover it when I look at the timeline to discover the last notification is from hours ago.

2. Probably a bug:  
While I test AdvancedFlow, it seems it triggers a rate-limit pretty fast. This happens with Aflows with just one timeline notification card. It’s not I test run every 1s for 60times. Just a few test runs seems to trigger the rate-limit.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 7, 2022, 5:44pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/2 "2022-10-07T17:44:13Z")

</div>

> [@Peter\_Kawa](#):
>
> Why isn’t an error message sent or present somewhere?

Why are you asking the community? 😜

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [October 7, 2022, 6:39pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/3 "2022-10-07T18:39:35Z")

</div>

Hey Peter,  
One thing: The Flow rate limit is NOT 60 executions a minute (afaik), but 60 runs at the same time (or at least without the others completing).

F.i. this flow:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/f/8f39a38f18a21976d69fa7228e87592353f22a6c.png)

This will run the same flow 70 times, well within a minute (i just found a bug that makes it run twice as many times, whoeps).

It was a bit tricky to build it, because the need to wait for the previous execution to run.

But it does work, and you can go through JSON Arrays/Collection with hundres of elements/objects in it, and loop through it using the same flow: No problem to execute this flow about 150 times a minute what i did during testing.

because i also thought it was 60 runs a minute, but, i have never hit that mark **as long as i put all executions after each the previous has completly finished.**

```auto
[TEF:FLOWS:H4sIAAAAAAACA5WSTW/cIBCG/8qKM6wwNmBz6yltFDWH7W21sjCMN+76qzauEq383wt2oiiKW21PaN4Zhnne4YocUlfU1vtf9TQ6GEjl9vdj137Vra1hWJJIofvD4/fdmzbjcKGtoB4tXLxy2dfd+a30UDV9DbuHxzs0+0qN1PGKKp9I44TqtDAEJDckEdYSzURMaETL0iZRHGeA8NLjB4xu99B1vY8BKTdMgJEJL6RREQlpI8KNzEhCQRLNjSZMlJAKSTNmbKh7RiqlGL0gxag/O9/0qWvgRem+V3/HxcukbqjOZxjyvPYj5LmDZxf5lHtP+Wj0YIh7IiZLSmjCBUniiJEsS0sSU5YVVotIGECnxQXvjm7g/USB72cgtjCaoepd1QX2L7pt9AVa756376YHVl6e/Av407pW1G9tP7l8jQOfNssYrxMva0XH4yu1UrfYr1Sw7beuJ2inpoDhdFp/AhOslFlGwOqSJJxroo20RGTWNyso5ZJ9XF0s/nt16/xbm/tIdtsuDlCDcbD++dAyuBFhhmOcYI4FljjFGY4o/iyyLTHeEpMtkW+JYkuUNPg7z6f5D6+BCznOAwAA]

```

---

<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:** [October 7, 2022, 7:48pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/4 "2022-10-07T19:48:57Z")

</div>

Sorry Arie, it’s about the timeline getting rate limited

---

<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:** [October 7, 2022, 8:03pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/5 "2022-10-07T20:03:41Z")

</div>

> [@robertklep](#):
>
> Why are you asking the community? 😜

Hehe, well, maybe someone can fix it, and by accident works for Athom 🙃

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [October 7, 2022, 8:24pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/6 "2022-10-07T20:24:33Z")

</div>

Yeah, i know, i just wanted to let you know the flow limit is not (60 a minute), what many people seem to think. 😉

---

<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:** [October 7, 2022, 8:37pm UTC](https://community.homey.app/t/timeline-rate-limit-without-error-notification/70046/7 "2022-10-07T20:37:04Z")

</div>

Ah okay, I knew 😉

> [@\[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…
