Fix a conversation that failed
When an agent can’t finish a request, the conversation’s status changes to Failed. Under the last message, Enjoy shows a one-line reason, the agent’s own error under Details, How to fix this, and Retry.
Steps
Read the reason
The first line says what went wrong in plain words. Details below it shows the original error. Select Details to hide or show it. When the reason comes down to the agent’s account, such as an expired sign-in, a usage or request limit, or a model the account can’t use, the account the agent was using appears under it, such as sam@example.com.


Fix the cause
Select How to fix this, before Retry. The Manual opens at the section below that matches the reason. Some causes, like a dropped connection, only need a retry.


Select Retry
The agent continues the request where it stopped, keeping the work it already did. If it never got your message, Enjoy sends the message again. The conversation shows Trying again… while it starts.
Or retry with different settings
If you change the agent, model, effort, speed, or permissions in the message box first, a second button appears, starting with Retry with and naming what changed. Select it to run the request with those settings.


Good to know
- In a project inside WSL, Details can say that the Linux distribution stopped during the agent’s work, as in Ubuntu-22.04 stopped while Claude Code was running., or that the agent couldn’t start there, as in Ubuntu-22.04 couldn’t start Claude Code: followed by why. Select Retry, which starts the distribution again. See Fix problems with a project in WSL.
- Messages you queued before the conversation failed wait. Enjoy shows Queue paused. Send a message or retry to continue. A message you queue after it failed goes when its turn comes.
- Sending a new message also continues the conversation.
- The same reason and the full error also appear at the top of the agent activity panel. Select Show agent activity, the last button at the top right of the conversation, to open it.
- If the same request keeps failing, a new conversation with a clear summary of what you need often works better. See Start fresh when a conversation gets long.
- When you contact support, copy the text under Details into your email. See What to include when you ask for help.
If something goes wrong
This request couldn’t finish.
Enjoy didn’t recognize the cause. Read Details for the agent’s error, then select Retry.
The connection dropped.
The connection to the agent’s service was interrupted. Check your internet connection, then select Retry.
Your sign-in session expired.
Select Sign in and finish in your browser. The conversation continues on its own, along with any others the expired sign-in stopped in the last day on that account. A conversation that stopped longer ago stays as it is, so select Retry when you want it to continue. On the web, sign in from Enjoy on your desktop instead. See Fix an agent that won’t sign in.
Sign in to [agent], then retry.
The message names your agent, which isn’t signed in on your computer. In a project inside WSL, Details adds that the project uses the agent in its Linux distribution, where you sign in separately. Open the agent settings in the message box and select Sign in under the agent’s name. When you’re signed in, select Retry. See Fix an agent that won’t sign in.
Install [agent], then retry.
The message names your agent, which isn’t installed on your computer. In a project inside WSL, Details adds that Enjoy runs the project’s agents in its Linux distribution, and the agent isn’t installed there, even if it’s on Windows. Open the agent settings in the message box and select the agent, which shows Install under its name. When it’s installed, select Retry. See Fix an agent that won’t install.
[Agent] couldn’t connect.
Enjoy couldn’t start or reach the agent on your computer, and Details gives the reason. Enjoy may also show Reconnect above your conversations or at the top of the project, which checks the agent again. Select it, then select Retry.
Your computer is running low on resources. Stop some running agents or processes, or quit other apps, then retry.
The agent couldn’t start because your computer ran out of memory, or of files it can keep open at once. Every agent that’s working uses some, and so does every process an agent keeps running, such as a website server. Enjoy has no limit of its own on how many agents run at once. To make room:
- Stop processes you no longer need. See Stop a background process.
- Stop agents you don’t need right now. See Stop an agent.
- Quit other apps you aren’t using.
Then select Retry. Older versions of Enjoy ran at most 24 agents at once and showed Process limit reached under Details. Update Enjoy to remove that limit. See Update Enjoy.
The usage limit was reached.
The agent’s plan ran out of usage for now. By default, Enjoy switches to another of your accounts for the agent that still has usage, or waits for the usage to reset when none does, and the conversation shows Waiting for usage. You see this failure when When usage runs out is set to Stop on the General page in Settings, or after you select Stop waiting. Select Wait and resume to have the conversation continue on its own once the usage resets, or Retry to try now. See What to do when an agent runs out of usage.
The request limit was reached. is different: the agent got too many requests in a short time. Wait a little, then select Retry.
This account can’t use the selected model. Choose another model, then try again.
The agent’s current account doesn’t include that model, for example after you switched accounts. Choose another model in the message box, then select the Retry with button.
This conversation is open in another app. Close it there, then retry.
The same agent session is open somewhere else, such as in a terminal. Close it there and select Retry. Or select Start a new session: the agent continues from this conversation’s history in a fresh session.
Your organization’s [agent] policy blocks the tools Enjoy needs. Use another agent, or ask your IT team to allow Enjoy.
Your workplace’s settings for that agent don’t allow the tools Enjoy adds to it. Choose another agent in the message box and select the Retry with button, or ask your IT team to allow Enjoy.
This saved work couldn’t be verified.
Enjoy couldn’t verify the saved request against its separate record on the computer running this project. Details now distinguishes a missing reference, a missing or unreadable record, an invalid record, a different project, and content that no longer matches. This does not necessarily mean you edited anything outside Enjoy. Older versions show “Saved work changed or its origin record is missing.”
If Details says Enjoy couldn’t read the record, select Retry. If it keeps failing, restart Enjoy on the computer running the project, then retry.
For the other causes, review your request and send it again as a new message. For a workflow, open it in Workflows, check its instructions and schedule, save it again, and run it again. See Edit a workflow. Retrying the same failed request does not recreate or repair its verification record.
If this happens during ordinary use, copy all of Details into your feedback, including the Verification, Work, Project, and Record lines when present. They identify the failed check and saved records without including your request’s text.
This conversation couldn’t load.
The status says Couldn’t load. Enjoy couldn’t read all of the conversation’s saved files, so there’s no Retry and no message box. Its files are kept as they are, and when the conversation’s files can be read, it opens by itself. Details says which file and why:
- Its older messages … haven’t arrived in this project’s storage yet. A long conversation keeps older messages in a file of their own, and that file is still on its way, for example from a cloud folder or another computer. Wait for it to arrive.
- Its older messages … aren’t in this project’s storage. If this storage is kept in Git, the file may not have been committed. Get the missing file from the computer or commit that has it, or restore the conversation’s folder from a backup.
- … is still downloading from your cloud storage. Wait for the download to finish.
- … can’t be downloaded from your cloud storage: followed by why. Start the cloud app and sign in, free some disk space, and allow Enjoy to download files.
- … can’t be read: followed by why. Another program may be holding the file, or its permissions may not allow reading. Close the program or fix the permissions.
- … doesn’t hold the messages messages.md lists for it. The files may still be syncing, or another program changed one. Wait for syncing to finish, or restore the conversation’s folder from a backup.
- … is damaged: followed by why. Restore the conversation’s folder from a backup, or delete the conversation.
- It was saved by a newer version of Enjoy. Update Enjoy to open it. Update Enjoy. See Update Enjoy.
- It was saved by a newer version of Enjoy, which this version can show but not change. You can read the whole conversation, but not continue it here. Update Enjoy to continue it.
- It was partly deleted: Enjoy couldn’t remove one of its files, for example because another program held it. Delete it again to finish.
Delete conversation always works, whatever Details says, and removes every file of the conversation, including ones Enjoy can’t read. See Delete a conversation and Fix a file that won’t save or load.