Our solution is randomly (seemingly) getting this error:
I think it has something to do with nesting re-useable components, as I’ve been able to get it to go away (temporarily) by re-binding component parameters inside a component that is used inside another component.
But my bug fixing for this issue has been a bit too chaotic to identify exactly what the trigger is.
Any tips for future bug fixing?
Hi,
The error message “Maximum call stack size exceeded” typically indicates that there’s some form of infinite recursion happening—often due to a component calling itself indirectly, or parameters being passed in a way that causes repeated re-evaluation. From your description, it sounds like nesting reusable components and binding parameters within those could be triggering this kind of loop.
Unfortunately, without a reproducible example, it’s difficult to pinpoint the exact cause. If it happens again, and you’re able to share either the model setup or a minimal reproduction case, we’d be happy to take a closer look. Alternatively, if you’re open to it, we could transfer the model to our internal dev environment to investigate further.
In the meantime, keeping an eye on recursive patterns—especially when re-binding parameters inside deeply nested components—might help avoid this issue. Let us know if it resurfaces or if you’re able to narrow down a more specific trigger.
Malin
