> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aihubmix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors and recovery: send failures, device disconnects, cloud server updates, sleep, and usage limits

> What you see when a session or message runs into an error, which cases recover automatically, and which need you to retry, resend, or switch sources.

This page lists problems you may run into while a session runs or a message is sent, and what you need to do. General rules: **what you write is not lost** (when sending fails, the message is kept and you can retry), **completed steps and files are not lost** (changes and the environment are kept after an interruption), and **anything that can recover automatically does**.

## Availability

| Platform | Support | Notes |
| - | - | - |
| Desktop app | Supported | When a session runs on this computer, actions such as **Reconnect** are available after a disconnect |
| Web app | Supported | |
| Mobile web | Supported | |

## Quick reference

| Situation | What you see | What you can do |
| - | - | - |
| Message not sent | **This step couldn’t finish** below the message | Click **Retry** |
| Connection to the server lost | **Connection lost. Reconnecting, missed messages will catch up automatically** | Wait. Refresh the page when it shows **Disconnected. Please refresh the page** |
| Execution device disconnected | **The device running this task disconnected. This turn is paused and continues automatically when it reconnects.** | Wait, or click **Reconnect** on that device |
| Cloud server updating | **Your cloud server is updating, retrying automatically** | Wait |
| A cloud server upgrade, shutdown, or replacement interrupted this turn | "…this turn stopped…" | Click **Resend**, or send a message to continue |
| Session asleep | **This chat is asleep and wakes when you send a message** | Send a message |
| Session queued | "Queued: …" | Wait. It starts automatically when a slot frees up |
| Session paused | **Chat paused: reason. Resolve it to continue** | Resolve according to the reason |
| Your subscription hit its usage limit | **Account usage limit reached** dialog | Switch accounts, switch models, or wait |
| No Plus plan | Fixed reply + upgrade card | See [Sending without Plus](https://docs.aihubmix.com/en/cloud/plus/without-plus.md) |

## Message send failures

When a message is not sent, a **This step couldn’t finish** card appears below the message: **The connection was interrupted. Your message hasn’t been sent and is kept here. Try again.** Click **Retry**. On success, the card changes to **Recovered**. Retrying does not send the same message twice.

When the first message sent from the new chat page fails, the message is marked **Not sent: reason**. Click **Retry** in the same way.

## Connection to the server

When the connection is interrupted, the area above the composer shows **Connection lost. Reconnecting, missed messages will catch up automatically**. After it recovers, messages from the disconnected period are filled in automatically. If it cannot recover, it shows **Disconnected. Please refresh the page**; refresh the page. When the browser is fully offline, it shows **You’re offline**.

## Auto-continue after the execution device disconnects

When a session runs on your device and that device disconnects (shut down, asleep, offline, and so on), the turn pauses, and all clients show **The device running this task disconnected. This turn is paused and continues automatically when it reconnects.** After the device reconnects, the turn continues automatically from where it was interrupted, and completed operations do not run again. If you sent a message manually or clicked stop while paused, it does not resume automatically. After repeated disconnects, it may also stop resuming automatically; in that case, send a message.

The desktop app on the execution device shows the disconnect reason and **Reconnect**. Handle it according to the reason:

| Shows | What you can do |
| - | - |
| The cloud closed the connection or is updating; **No network connection. Reconnecting automatically** | Wait |
| **Your sign-in expired. Sign in again to reconnect automatically** | Sign in again |
| **Execution machine unavailable: execution isn’t allowed on this computer** | Turn on **Allow execution** in **Machines & access** |
| **No folder is linked to “project name” on this computer yet** | Click **Link folder** |
| **The local service quit unexpectedly several times. Automatic restart stopped** | Click **Restart** |
| **You disconnected this task from running on this computer** | Click **Reconnect** |

For the device's connection status and execution log, see [Run environment](https://docs.aihubmix.com/en/cloud/projects/run-environment.md).

## Cloud server updates, upgrades, and shutdowns

| Situation | Timeline shows | What you can do |
| - | - | - |
| The cloud server is updating | **Your cloud server is updating, retrying automatically** | Wait. It retries automatically after the update |
| An upgrade interrupted this turn | **Your cloud server upgraded and this turn stopped. You can resend** | Click **Resend** to send your last message again |
| Stopped or replaced, environment temporarily unavailable, or run failed | "Your cloud server stopped or was replaced, so this turn ended…", "This turn was interrupted (the environment is temporarily unavailable…)", **Run failed. Output is kept** | Send a message after the environment is ready, and the Agent continues from the existing progress |

## Sleep, suspension, and wake-up

* Sessions with no activity for a while go to sleep and show **This chat is asleep and wakes when you send a message**. Just send a message.
* While the cloud server is resuming, the timeline shows **Wake environment project name**, and messages you send are sent automatically once the environment is ready. If resuming fails, you are guided to subscribe or renew.
* When a session is suspended, the reason follows the status (for example, **Stopped at expiry** or **Failed to start. Send another message to retry**). Follow the prompt.

## Session queue

Up to 5 sessions can run at the same time in one project. When the limit is reached or the cloud server is resuming, new sessions are queued and start automatically in order when a slot frees up. Messages you send while queued are handled once it starts.

## Session paused

When a session is paused, the sidebar shows **Needs your input**, and the session shows **Chat paused: reason. Resolve it to continue**:

| Reason | What you can do |
| - | - |
| **Model usage limit reached** | See "Plan limits reached" below |
| Subscription account disconnected, **Subscription inactive**, **Sub-key no longer valid** | Switch sources or models to continue (when the subscription account is disconnected, click **Use another model** in the dialog) |
| **Pending request timed out** | Send a message to continue |
| **Waiting for configuration** | Complete the configuration as prompted |
| **The device running this task disconnected. It continues automatically when it reconnects** | See "Auto-continue after the execution device disconnects" above |
| **Account suspended** | Contact support |

## Stop this turn

Click **Stop this turn** or press `Esc`:

* The timeline records **This turn stopped. Finished steps and files are kept.** Keep sending messages to continue.
* Requests still waiting for you are discarded.
* Queued messages are sent in their original order. When this turn was stopped elsewhere, the queue pauses. See [Composer](https://docs.aihubmix.com/en/cloud/sessions/composer.md).

Editing an earlier message during a run stops the current turn first. If stopping times out, it shows **Stopping timed out. Try again, your edit is kept.** Click **Rerun** again a little later.

## Plan limits reached

When you use your subscriptions (for example ChatGPT or Claude accounts) and that account hits its usage limit, the session stops and the **Account usage limit reached** dialog opens. It states which limit was reached and roughly when it resets. Finished changes and the environment are kept. You can:

* When you have other accounts from the same provider: choose an account and click **Continue with this account**.
* When you have no other accounts: click **Add account** or **Use another model**.
* **Later**: closes the dialog. Continue after the limit resets.

You can view usage in **Settings › Usage**. See [Usage and billing](https://docs.aihubmix.com/en/cloud/settings/usage-and-billing.md).

## Error cards above the composer

When sending, uploading, previewing, connecting, or other actions fail, the error appears directly above the composer with a description and a primary action. Multiple errors stack, and you can expand them, **Collapse**, or **Dismiss all**. When a retry succeeds, the card shows **Recovered** and disappears automatically. **Details** contains the original error message, and you can use **Copy details** when contacting support.

| Error | What you can do |
| - | - |
| **You’re offline**, **Request timed out**, **Too many requests**, **Service unavailable**, **Something went wrong** | Click **Retry** or wait for the automatic retry. If it keeps failing, copy the details and contact support |
| **Your session expired** | Click **Sign in**. Chats and drafts are kept |
| **You don’t have access** | Contact a workspace admin |
| **File too large**: **File name is over 20 MB. Compress or split it and try again.** | Compress or split the file |
| **Couldn’t open the preview** | Make sure the dev server is still running and listening on `0.0.0.0`, then click **Retry** |
| **This source isn’t available right now. Try another source or model** | Switch sources or models |

## FAQ

### The session was interrupted. Are the files changed earlier still there?

Yes. Whether you stopped the turn, the cloud server was upgraded or stopped, or the execution device disconnected, completed steps and files are kept. Send another message to continue.

### What is the difference between "Resend" and sending a new message?

**Resend** sends your last message again unchanged. You can also send a new message, and the Agent continues based on the earlier progress.

### What do I need to do after the execution device disconnects?

Usually nothing. After the device reconnects, the session continues automatically. You can also click **Reconnect** in the app on that device.

## Related

* [Composer](https://docs.aihubmix.com/en/cloud/sessions/composer.md)
* [Needs your input](https://docs.aihubmix.com/en/cloud/sessions/user-intervention.md)
* [New session](https://docs.aihubmix.com/en/cloud/sessions/new-session.md)
* [Run environment](https://docs.aihubmix.com/en/cloud/projects/run-environment.md)
* [Messages and session actions](https://docs.aihubmix.com/en/cloud/sessions/messages.md)
* [Sending without Plus](https://docs.aihubmix.com/en/cloud/plus/without-plus.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.