# Advanced Flow API update caused Flow UI to fail

**URL:** <https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290>\
**Category:** Questions & Help\
**Tags:** advancedflow\
**Created:** [August 14, 2026, 12:46pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290 "2026-08-14T12:46:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sethakan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sethakan/32/55863_2.png) [@Sethakan](https://community.homey.app/u/Sethakan)\
**Post date:** [August 14, 2026, 12:46pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290/1 "2026-08-14T12:46:14Z")

</div>

Hi,

I experienced an issue on my Homey Pro after an Advanced Flow was modified through the ChatGPT/Homey integration.

The affected flow was called “Beräkna kostnad per kWh”.

After the integration updated the Advanced Flow by adding extra cards and error-path connections (`outputError`), the Flow section in Homey stopped working and showed:

`RangeError: Maximum call stack size exceeded`

At the same time, the API temporarily returned no flows at all. After restarting Homey Pro, the flows became accessible again. The affected Advanced Flow was then restored to its previous, simpler structure, and everything returned to normal.

The flow currently reports:

`enabled: true`  
`broken: false`

Could you please investigate whether the Advanced Flow API can accept and save a flow structure that passes API validation but causes the Flow UI or flow engine to hit a recursive/circular condition and exceed the call stack?

It would be helpful if the API rejected such structures before saving them, rather than allowing a configuration that can affect access to the Flow section.

Best regards,  
Håkan

---

<div class="post-metadata">

**Author:** ![Sethakan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sethakan/32/55863_2.png) [@Sethakan](https://community.homey.app/u/Sethakan)\
**Post date:** [August 14, 2026, 12:48pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290/2 "2026-08-14T12:48:52Z")

</div>

I just wat to add that everyting was made by chat gpt, also the text above. I just want support to know this so they can fix it.

---

<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:** [August 14, 2026, 12:53pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290/3 "2026-08-14T12:53:07Z")

</div>

If you need to contact Athom about this, you have to do so via the Support website: [https://support.homey.app](https://support.homey.app)

This is a community forum that Athom doesn’t use for reports like this.

---

<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:** [August 14, 2026, 2:58pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290/4 "2026-08-14T14:58:35Z")

</div>

Am I right when this AI stuff edits your _original_ flow instead of a copy for you to evaluate?  
Or did you let it edit your original flow by choice?

Just wondering how much trust some folks in general put into AI …

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 14, 2026, 3:01pm UTC](https://community.homey.app/t/advanced-flow-api-update-caused-flow-ui-to-fail/158290/5 "2026-08-14T15:01:08Z")

</div>

You usually have to approve it first. So the AI makes a tool call and for the edit Flow tool, you can decide if you want to approve the call or decline it each time, or if it should always approve/decline by default
