Document Could Not Be Autosaved - Your Most Recent Changes Might be Lost

Hi, this has happened once or twice in the last 113 versions of my file, but seemed to resolve quickly... but this time I cannot proceed (tried for the last hour).... I "simply" used the Option key and "Save As" version 113 (it was v112) and as soon as I do a few light edits this warning keeps repeatedly coming back:


Document Could Not Be Autosaved.


Apple seem to make what used to be simple, a tedium... 25 yrs using Apple I think I am qualified to state this.

Yes, Feedback... They don't listen. They used to when I (very rarely) needed to write to the Ireland Customer Relations department... I really don't know what has happened at Apple in the last few years, but I have unexpected behaviour on the M2 and iphone, all the time, every day, different apps... ok, complaining over.


#BringBackMojave


Thanks.

MacBook Pro 16″

Posted on May 28, 2025 5:14 AM

Reply
Question marked as Top-ranking reply

Posted on May 28, 2025 5:37 PM

This could be a permissions thing. Is the file "locked"? In Finder navigate to it, right-click, choose Get Info.


If sharing is turned on you could try turning it off.


SG

Similar questions

4 replies

May 28, 2025 10:07 AM in response to Bardonicloud

Hi, this has happened once or twice in the last 113 versions of my file, but seemed to resolve quickly... but this time I cannot proceed (tried for the last hour).... I am in an endless cycle of force quits / unsaved documents etc.


|I used the Option key and "Save As" version 113 (it was v112) and as soon as I do a few edits this warning keeps repeatedly coming back:


"Document Could Not Be Autosaved."


I can't even quit the program now as it says "Not Saved." And it prompts the Duplicate/Discard pop up....


If I hit Duplicate, on the warning, it crashes...


So I have to hit discard...


Why is it saying "Untitled" in the title at the top of the file and yet when I hit File/Rename there is no "Untitled in the name?" Which is it? Untitled or the name I gave it?


A lot of memory is being used too.


Apple Support said that this is a known bug.


The fix apparently is to create a separate tab and make a table with some simple numbers in it. Then go to Organise (top menu) and create a pivot table on the "current sheet," and then tick Column B (to the right). This is the (odd) workaround. I have no idea how this fixes the problem and wish I was working on the document that we created the extra pivot tab table in because the latter document I am working on without the "fix" has now also failed to save....


Any other ideas how to stop this?


Thanks.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Document Could Not Be Autosaved - Your Most Recent Changes Might be Lost

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.