# InfiniteLoop runtime error

**URL:** <https://forums.unrealengine.com/t/infiniteloop-runtime-error/2708850>\
**Category:** Verse\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [March 25, 2026, 12:26pm UTC](https://forums.unrealengine.com/t/infiniteloop-runtime-error/2708850 "2026-03-25T12:26:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xxXenurXxx](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@xxXenurXxx](https://forums.unrealengine.com/u/xxXenurXxx)\
**Post date:** [March 25, 2026, 12:26pm UTC](https://forums.unrealengine.com/t/infiniteloop-runtime-error/2708850/1 "2026-03-25T12:26:09Z")

</div>

I’m encountering an **InfiniteLoop runtime error** that appears only occasionally in my project **UI\_Mechanics**. The issue is difficult to diagnose because the map has over **500 hours of playtime daily** , yet the Verse crash happens very rarely and I haven’t been able to recreate it.

The project contains **20+ Verse scripts with many lines of code** , so its hard to find what is causing it. After spending many hours investigating, I still haven’t identified which script, or which function is causing the crash.

Is there a way to determine **which specific script or function triggers the InfiniteLoop runtime error** in Verse? Any debugging method, logging approach, or tooling that could help isolate the issue would be very helpful.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/d/2/4d2813c7fbfbd817518fece74c34a1ddcdc8592a.jpeg)

---

<div class="post-metadata">

**Author:** ![Abrizzer](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Abrizzer](https://forums.unrealengine.com/u/Abrizzer)\
**Post date:** [March 25, 2026, 2:07pm UTC](https://forums.unrealengine.com/t/infiniteloop-runtime-error/2708850/2 "2026-03-25T14:07:47Z")

</div>

Hi! for what it’s said in the error, the problem should be a method that will call itself at the end of it or in the stack call, ends calling itself again, causing the recursion if it happens rarely, I would assume it probably has the “ **suspends** ” effect, at it’s something that runs really slow. So it needs time to happen and reach the max stack call. If it’s something like this, you could add the **spawn** when it calls to itself, to avoid the recursion.
