# Ignition Designer seems to be frozen

**URL:** <https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404>\
**Category:** Ignition\
**Tags:** perspective, vision\
**Created:** [September 5, 2025, 11:32am UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404 "2025-09-05T11:32:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andy.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@andy.hernandez](https://forum.inductiveautomation.com/u/andy.hernandez)\
**Post date:** [September 5, 2025, 11:32am UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404/1 "2025-09-05T11:32:20Z")

</div>

Ignition Vision:

I’m hoping someone can help me. I’m using Ignition Designer, but it seems to be frozen. I’ve tried power cycling the computer and restarting Ignition Designer several times, but it remains stuck. There’s a window open (screenshot below) that I can move around by dragging it, but I’m unable to click on the **Yes** , **No** , or **Cancel** buttons. Does anyone know how I can get past this?

 ![Ignition Designer Frozen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/8/388ab4000a46bea7b0ccc6ca543ad290ac1df26c.png)

This window just opened up but I’m unable to expand it or copy the message.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/8/98b1f185291ec7d736c8fc66e0de2306f716444a.png)  
I have no problems opening any other project.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 5, 2025, 12:06pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404/2 "2025-09-05T12:06:05Z")

</div>

Non-responsive UI. That means some event script is hogging the UI thread, typically with some kind of sleep or infinite loop (including wait loops). Such are not allowed in Vision UI events. In my experience, this is **always** a programmer error.

Those thread dumps it reports should be examined for the culprit task. If you cannot understand the contents, post one here (with code styling), or open an IA support ticket for them to look at.

---

<div class="post-metadata">

**Author:** ![andy.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@andy.hernandez](https://forum.inductiveautomation.com/u/andy.hernandez)\
**Post date:** [September 5, 2025, 12:08pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404/3 "2025-09-05T12:08:10Z")

</div>

What can I do to gain back control or how can I “Unfreeze” the designer?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 5, 2025, 12:14pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404/4 "2025-09-05T12:14:14Z")

</div>

You can't. You have to kill it from the OS. Then, don't open the problem window. Extract its XML formal (without opening--shift-right-click) and hand edit it to delete the problem script. (You may need help with that, too--the format is cryptic.) But don't try this part until you determine which script is killing your UI.

---

<div class="post-metadata">

**Author:** ![andy.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@andy.hernandez](https://forum.inductiveautomation.com/u/andy.hernandez)\
**Post date:** [September 5, 2025, 12:35pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-seems-to-be-frozen/110404/5 "2025-09-05T12:35:03Z")

</div>

I managed to find a backup that contained nearly everything, with only a couple of hours of work missing, and I was able to successfully import it back into the designer. Thank you very much for your help. I believe this issue is now resolved. By the way, you were absolutely right—it turned out to be a problem with poorly written expression logic.

Thanks again.
