# Lately alot of cards not triggering anymore or triggering unreliable - how to debug? **URL:** \ **Category:** Questions & Help\ **Created:** [January 10, 2025, 9:58am UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229 "2025-01-10T09:58:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Takie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/takie/32/86573_2.png) [@Takie](https://community.homey.app/u/Takie)\ **Post date:** [January 10, 2025, 9:58am UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/1 "2025-01-10T09:58:07Z")
For some unknown reason, multiple unaltered flows of mine that were reliable, have started to trigger unreliable as of late. Mostly related to Philips Hue (via bridge) and home/away location. All my location settings on the related phones look fine (Homey allowed to always run in background, enhanced location accuracy etc…). And in Homey I don’t see any cpu or ram overload. While designing the flows I also made sure that simultaneous triggers have a different delay to avoid concurrency issues. Is there anything else I can try to find the issue(s)? ---
**Author:** ![Takie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/takie/32/86573_2.png) [@Takie](https://community.homey.app/u/Takie)\ **Post date:** [January 10, 2025, 12:33pm UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/2 "2025-01-10T12:33:44Z")
Forgot to mention: I did change languages a while ago in Homey. Could it be that certain cards are now broken because of this? E.g: I now have several cards with a mixture of dutch and english: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/c/ec59a1c10a6af3af4423f2ed69325d9f4cf3a7ff.png) While if I recreate it it says: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/d/3dee2f041238681d3904e787f6927f1e11d798a5.png) ---
**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 10, 2025, 1:22pm UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/3 "2025-01-10T13:22:02Z")
Whenever I change names of devices or variables, I check the flows I use them in. Quite often I need to replace or change them manualy. ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [January 10, 2025, 1:51pm UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/4 "2025-01-10T13:51:10Z")
Try reboot the Homey? ---
**Author:** ![Takie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/takie/32/86573_2.png) [@Takie](https://community.homey.app/u/Takie)\ **Post date:** [January 10, 2025, 1:52pm UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/5 "2025-01-10T13:52:31Z")
Tried that already several times. As well for individual apps ---
**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 10, 2025, 6:45pm UTC](https://community.homey.app/t/lately-alot-of-cards-not-triggering-anymore-or-triggering-unreliable-how-to-debug/127229/6 "2025-01-10T18:45:02Z")
> [@Takie](#): > > several cards with a mixture of dutch and english: I watched the same phenomenon with flows I didn’t look at for ages, while I was troubleshooting Sun Events cards. I changed Homey’s language from NL to EN long time ago, and Homey got rebooted after every firmware update for sure. So that won’t solve it.