# Force closed designer after infite loop - days worth of progress lost

**URL:** <https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032>\
**Category:** Ignition\
**Created:** [October 26, 2023, 1:48pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032 "2023-10-26T13:48:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Remco\_Geervliet](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@Remco\_Geervliet](https://forum.inductiveautomation.com/u/Remco_Geervliet)\
**Post date:** [October 26, 2023, 1:48pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032/1 "2023-10-26T13:48:27Z")

</div>

As you can probably deduct from the title - I've made a rookie mistake..

After accidentally locking my entire designer up by starting preview mode before finishing my script, I force-closed it via task-manager.  
Expecting to have lost my changes since the last time I saved, it turns out I lost all changes since the last time I closed the designer.

When opening back up again, I got notified 'another user' was working in the same project and saving could result in conflict. I started to take stock of what exactly I hadn't saved since earlier this afternoon, but discoverd all my changes of the past days (since I've opened the designer, essentially) had been lost instead.

As the designer seems to think 'another user' is still working in the project, is there a way for me to retrieve what was lost, do I wait until the session times out, or am I just going to have to redo the last 3 days' worth of work?

---

<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:** [October 26, 2023, 1:53pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032/2 "2023-10-26T13:53:26Z")

</div>

Wait for the timeout. Should not be long. Grab a gateway backup while you wait.

(Use git or regularly take gateway backups to capture forward progress.)

---

<div class="post-metadata">

**Author:** ![Remco\_Geervliet](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@Remco\_Geervliet](https://forum.inductiveautomation.com/u/Remco_Geervliet)\
**Post date:** [October 26, 2023, 2:09pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032/3 "2023-10-26T14:09:17Z")

</div>

It was, in fact, not long. I've grabbed a back-up and from what I can tell only some graphic updates from this afternoon were lost - not the scripts I've spent the last three days on. Thank you.

Is there a way to exit preview mode besides the toolbar-button? In case I make another oopsie ..

---

<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:** [October 26, 2023, 2:10pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032/4 "2023-10-26T14:10:53Z")

</div>

No, infinite loops are infinite. Unless in the script console. I think ctrl-C does work there. Or there's a kill button. (Can't remember the last time I did similar.)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 26, 2023, 3:48pm UTC](https://forum.inductiveautomation.com/t/force-closed-designer-after-infite-loop-days-worth-of-progress-lost/81032/5 "2023-10-26T15:48:27Z")

</div>

> [@pturmel](#):
>
> I think ctrl-C does work there. Or there's a kill button. (Can't remember the last time I did similar.)

Both do, yes.
