# \[Feature Request\] - "WHEN" "A Push notification was sent"

**URL:** <https://community.homey.app/t/feature-request-when-a-push-notification-was-sent/136004>\
**Category:** Ideas & Suggestions\
**Tags:** flow, featurerequest\
**Created:** [May 5, 2025, 7:32am UTC](https://community.homey.app/t/feature-request-when-a-push-notification-was-sent/136004 "2025-05-05T07:32:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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 5, 2025, 5:46pm UTC](https://community.homey.app/t/feature-request-when-a-push-notification-was-sent/136004/3 "2025-05-05T17:46:32Z")

</div>

Too many push or timeline notifications in a certain amount of time gets the service “rate limited” by Homey (not your phone). It just quits temporarily.  
No one knows the exact conditions.

Solved by waiting 24h / Homey restart.

Consider adding the [CallMeBot app](https://community.homey.app/t/48374)’s Signal or Telegram services as second notification service and split the load.

---

_[View the full topic](https://community.homey.app/t/feature-request-when-a-push-notification-was-sent/136004)._