Fix a file that won't save or load
Enjoy saves docs and project files by itself as you type. The bar at the bottom of the editor shows how it’s going: Saved, Unsaved changes, Saving…, Not saved, or Conflicting changes. Whatever goes wrong, Enjoy keeps your draft until it’s saved somewhere.
Steps
Check the bar at the bottom
Saving… means Enjoy is still writing, so give it a moment. Not saved means it tried and failed. Conflicting changes means the file changed somewhere else while you edited. See What happens when a file changes while you edit it.
Read the message, then select Retry save
A message above the editor says what went wrong. Fix the cause using the matching section below, then select Retry save.


Keep your version safe if it still won’t save
For a project file, select Save a copy to put your version in a new file next to the original. If the file is open beside a conversation, open it in Files first, with the folder button above it.
Watch for a message at the top of the project
Unable to save changes: followed by a reason means Enjoy couldn’t write your project’s conversations, docs, or workflows to disk. Enjoy keeps the changes and tries again by itself, and the message goes away once a save works. Fix the reason it gives, such as a full disk.
Check for unavailable files
An amber warning icon at the end of your project’s section tabs, after Project settings, means some workspace files are unavailable. Select it to see which ones. See the section below.


Good to know
- A project file has to be under 500,000 characters and 2 MB to edit in Enjoy. Larger ones show This file is too large to edit here. Open them in another app instead. See Open a file in another app.
- If a doc’s bar says View only, you can read it but not change it here, for example on a computer someone shared with you as view only.
- Enjoy keeps each project’s conversations, docs, and workflows in the project’s storage folder. To find it, open Project settings, select Storage, then select the button that shows the folder, such as Show in Finder. See Choose where a project’s conversations are stored.
- In a project inside WSL, Enjoy saves project files in the Linux distribution, keeping a script’s permission to run and the file’s line endings. If the distribution stopped, saving starts it again.
- If you quit the computer app while a conversation can’t be saved, it says Could not save before quitting, names each conversation with the reason, and stays open. Quit again to close Enjoy without those changes. Restart to update, switching branches, moving storage and removing a project work the same way: the message names what isn’t saved, and doing it again goes ahead without those changes. On Windows and Linux, closing the window quits Enjoy.
- Each conversation saves on its own, so one that can’t be saved never stops your other conversations, docs, and workflows from saving.
If something goes wrong
This file is read-only. Your draft has been kept.
The file’s permissions don’t allow changes. Select Save a copy to keep your version in a new file. Or allow changes to the original outside Enjoy, then select Retry save.
Text files must be smaller than 500,000 characters and 2 MB.
Your edits made the file too big for Enjoy’s editor. Select Save a copy, or make the file smaller.
This file was removed. Your draft has been kept.
The file was deleted while you edited it. Select Save a copy to keep your version.
Some workspace files are unavailable
Select the amber warning icon at the end of your project’s section tabs, in the navigator. Its badge counts the files, and it opens a list of them under a title such as 2 files couldn’t be loaded. Their contents have been kept, and other files remain usable. These are files in the project’s storage folder that Enjoy couldn’t read, and Enjoy doesn’t change them. Each file in the list has the reason under it. If you have a backup of the folder, restore those files from it. For a conversation, restore its whole folder (the folder named after its ID, inside threads), not one file. Enjoy reads the files again by itself once they change. Otherwise, email help@enjoy.dev with the list. Select Dismiss to hide the warning; it comes back if a different set of files becomes unavailable.
This document couldn’t be opened
The doc’s saved file couldn’t be read. The original file has been preserved. Repair it on disk to continue. Until it’s repaired, Enjoy won’t edit, archive, or delete it. Follow the steps for unavailable files above.
Unable to read this project’s conversations, docs, and workflows
Enjoy couldn’t read the project’s storage folder, and the rest of the message says why, for example because the drive or disk image holding it is no longer connected. Agents in that project don’t start meanwhile, so nothing works from records Enjoy can’t see. Work that was already waiting keeps waiting instead of failing, and something new you send shows this message until the folder can be read. Reconnect the drive, or fix the reason the message gives. Once Enjoy can read the folder again, the message goes away and the waiting work starts by itself. Other projects keep working throughout.
This conversation couldn’t load.
The conversation’s status says Couldn’t load. Its saved files couldn’t be read, and their contents are kept. Select Details to see why. See Fix a conversation that failed.
“[Conversation]” isn’t being saved right now
Enjoy can’t read one of the conversation’s files at the moment, for example because it’s still downloading from your cloud storage or another program is rewriting it. Enjoy keeps your changes in the app and saves them once it can read the file. Meanwhile you can’t send new messages to that conversation. Wait for the file to arrive or finish downloading, or restore the conversation’s whole folder from a backup. If you quit, restart to update, or switch branches meanwhile, Enjoy names the conversation and stops; doing it again goes ahead and leaves those changes unsaved.
… can’t be downloaded from your cloud storage
The project’s storage is in a cloud folder, such as iCloud Drive or OneDrive, and a file is only in the cloud. Start the cloud app and sign in, free some disk space, and make sure Enjoy is allowed to download files. Enjoy tries again by itself when the file changes.
This conversation was changed by a newer version of Enjoy
Another computer or an earlier session saved this conversation with a newer version of Enjoy, which this version can show but not change. Update Enjoy to keep working in it. See Update Enjoy.
“[Conversation]” is too large to save
The conversation is over the 8 MB one file can hold, usually because of queued messages or a large draft. Remove queued messages or drafts from it, then try again. Your other conversations keep saving.
Unable to save changes
Followed by a reason, this means Enjoy couldn’t write anything, for example because the disk is full, the WSL distribution holding the project stopped, or the storage folder’s permissions don’t allow changes. Free disk space, start the distribution, or check the folder’s permissions. Enjoy keeps your changes and tries again by itself.
Enjoy couldn’t finish saving
When the message ends with It finishes the save as soon as it can., another program, such as an antivirus scanner or a backup app, is holding one of the conversation’s files. Enjoy kept the whole save and finishes it by itself once the program lets go. When the message says It kept that save in a file, the change can’t be written as things are, for example because a file’s permissions don’t allow it. Fix the reason it gives; Enjoy tries again when the files change, when you come back to the window, and before it quits.
Another Enjoy is saving this project’s storage right now
Another computer that opens the same storage folder, for example through a shared drive, is in the middle of a save. Try again in a moment. It clears within two minutes, even if the other computer stopped.
This conversation has too much waiting to be saved
Its queued messages, questions, drafts, and posts together would take more than a conversation can hold. Send or remove some of the queued messages first.
This project’s storage holds 100,000 conversations, questions, documents and other items
That’s the most Enjoy saves in one project. Delete conversations, questions, or docs you no longer need, then try again. Your existing work keeps saving.
A project that can’t open because an earlier save couldn’t finish
If Enjoy stopped in the middle of a save and can’t finish it when it opens the project, for example because another program still holds a file, the project shows as unavailable with the reason. Fix the cause, such as closing the program holding the file, then select Try again.
[Distribution] stopped, so Enjoy paused saving this project’s records.
This appears on the card at the top of the conversation list, for a project inside WSL whose conversations, docs, and workflows are still in a .enjoy folder in its Linux distribution. Enjoy keeps your changes and saves them once the distribution is back. Select Try again on the card. See Fix problems with a project in WSL.
Return to this document’s computer to finish saving. Your draft has been kept.
You switched to another computer before your edits were saved. Switch back, and the doc finishes saving by itself. For a project file, the message says Return to this file’s computer to finish saving. Switch back, then select Retry save. See What happens when a file changes while you edit it.