# Prompted to save Autosave Levels as actual new levels

**URL:** <https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334>\
**Category:** Feedback & Requests\
**Tags:** bug, unreal-engine, UE5-0, bug-report, editor\
**Created:** [May 7, 2022, 3:08pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334 "2022-05-07T15:08:55Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![VL4DST3R](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/vl4dst3r/32/482857_2.png) [@VL4DST3R](https://forums.unrealengine.com/u/VL4DST3R)\
**Post date:** [May 7, 2022, 3:08pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/1 "2022-05-07T15:08:55Z")

</div>

I noticed the longer i work the higher the chance the engine craps its pants and starts detecting its own autosaves as assets that need saving. If i do a Shift+S I can end up with 4-5 iterations of the same level (i aleady saved previously) but within the autosave subfolder, example:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/e/c/aec51b7c707c9e98aa026b749a2743d22cca95ca.png)  
If i do attempt to save those, the engine prompts me to save them as new, distinct levels, which is obviously not desired. Is this a known bug?

---

<div class="post-metadata">

**Author:** ![ObliviousJenn](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ObliviousJenn](https://forums.unrealengine.com/u/ObliviousJenn)\
**Post date:** [May 8, 2022, 12:20am UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/2 "2022-05-08T00:20:50Z")

</div>

I am having the same issue. I’ve only noticed it after testing level switching while playing in the editor, but that might just be coincidence.

---

<div class="post-metadata">

**Author:** ![VL4DST3R](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/vl4dst3r/32/482857_2.png) [@VL4DST3R](https://forums.unrealengine.com/u/VL4DST3R)\
**Post date:** [May 19, 2022, 12:34pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/3 "2022-05-19T12:34:28Z")

</div>

Bump. Coincidence or not, its clearly a bug. Any idea if they even check threads like these or if we should submit it somewhere else? The issue tracker is not open to the public.

---

<div class="post-metadata">

**Author:** ![TheWolf](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/thewolf/32/1036665_2.png) [@TheWolf](https://forums.unrealengine.com/u/TheWolf)\
**Post date:** [August 30, 2022, 8:20am UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/4 "2022-08-30T08:20:03Z")

</div>

Yup, very annoying. Anyone find a work around besides turning off auto-save?

---

<div class="post-metadata">

**Author:** ![mmflame](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@mmflame](https://forums.unrealengine.com/u/mmflame)\
**Post date:** [September 8, 2022, 12:50am UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/5 "2022-09-08T00:50:29Z")

</div>

same problem

---

<div class="post-metadata">

**Author:** ![Lexadoro](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/lexadoro/32/561427_2.png) [@Lexadoro](https://forums.unrealengine.com/u/Lexadoro)\
**Post date:** [September 14, 2022, 3:47pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/6 "2022-09-14T15:47:08Z")

</div>

same issue here

---

<div class="post-metadata">

**Author:** ![TheWolf](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/thewolf/32/1036665_2.png) [@TheWolf](https://forums.unrealengine.com/u/TheWolf)\
**Post date:** [December 6, 2022, 12:21am UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/7 "2022-12-06T00:21:05Z")

</div>

Still here in 5.1

---

<div class="post-metadata">

**Author:** ![VL4DST3R](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/vl4dst3r/32/482857_2.png) [@VL4DST3R](https://forums.unrealengine.com/u/VL4DST3R)\
**Post date:** [December 6, 2022, 9:52pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/8 "2022-12-06T21:52:44Z")

</div>

Yup, still in 5.1, but it seems a tad less often.

---

<div class="post-metadata">

**Author:** ![Fire\_Noodle](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Fire\_Noodle](https://forums.unrealengine.com/u/Fire_Noodle)\
**Post date:** [December 16, 2022, 6:03pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/9 "2022-12-16T18:03:44Z")

</div>

I’m still on 5.0.3 and it’s a real pain in the a\*\*. I’m very tempted to turn off the autosave feature altogether.

---

<div class="post-metadata">

**Author:** ![hectavex](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hectavex/32/88716_2.png) [@hectavex](https://forums.unrealengine.com/u/hectavex)\
**Post date:** [May 16, 2023, 10:40pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/10 "2023-05-16T22:40:53Z")

</div>

Still a bug in 5.1.1 not sure about 5.2…

---

<div class="post-metadata">

**Author:** ![slavensb](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@slavensb](https://forums.unrealengine.com/u/slavensb)\
**Post date:** [August 3, 2023, 11:31pm UTC](https://forums.unrealengine.com/t/prompted-to-save-autosave-levels-as-actual-new-levels/551334/12 "2023-08-03T23:31:31Z")

</div>

Yeah, this happens to me nearly every time I run the **Fix Up Redirectors** command on a folder in my project.

Once I’ve saved all the autos as “Untitled” over each other, the editor crashes with the fatal error:

```auto
Fatal error: [File: ..\Engine\Source\Runtime\TypedElementFramework\Public\Elements\Framework\TypedElementData.h] [Line: 276] 
Element 'World None.None - ID: 5' is still externally referenced when being destroyed! Ref-count: 2; see above for reference information (if available).

```

This happens every time I do this. Unfortunately, this is a hard crash, so the bug report window doesn’t even show up afterwards.
