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

# A chat failed or stopped — how to recover

> Option A — Retry the failed message.

## Symptoms

* You see **Chat Failed** on a message.
* The answer stopped part-way through and never finished.
* A banner reads **Reconnecting…** and the response paused.
* Your prompt shows **Will send when you reconnect** and hasn't sent.
* Chief retried itself and posted: "My re-try did not work. Trying one more time," or "I'm getting consistent failures."

## Likely causes

* [A brief network drop](/help/chatting-with-chief/working-offline-draft-preservation) interrupted the live response stream.
* You closed the tab or lost connection while Chief was still writing.
* An unusually long or complex request timed out.
* The project [ran out of credits](/help/plans-credits-billing/what-happens-when-you-run-out-of-credits) mid-answer.

## Solution

<Frame>
  <img src="https://mintcdn.com/chief-2d405d1a/ZjT7ckngTj8rjHF7/images/help/chat-offline-banner.png?fit=max&auto=format&n=ZjT7ckngTj8rjHF7&q=85&s=6fe12686d508587f7699d2ffaf25b01b" alt="Chief troubleshooting - the You are offline banner shown when a chat stalls" width="1380" height="96" data-path="images/help/chat-offline-banner.png" />
</Frame>

**Option A — Retry the failed message.**

1. Find the message marked **Chat Failed** in the chat thread.
2. Click the **Try again** (or **Retry**) control beneath it. Chief re-runs the same prompt and streams a fresh answer.

**Option B — You're offline or reconnecting.**

1. Look at the top of the chat for the **You're offline** or **Reconnecting…** banner. Your draft is saved — "Submissions are paused — your draft is saved."
2. Restore your internet connection. When Chief reconnects, any prompt showing the **Will send when you reconnect** pill sends automatically.
3. If you'd rather not wait, click **Cancel** on the pending prompt, then send it again once you're back online.

**Option C — The response stopped and you want a clean restart.**

1. If Chief is still working and the answer looks stuck, click [**Stop Generating**](/help/chatting-with-chief/regenerating-or-stopping-a-response) in the prompt bar to end the current run.
2. Re-send your prompt to start a fresh response.

<Warning>
  ⚠️ **Important:** You [can't delete a message](/help/chatting-with-chief/deleting-a-chat) while it's still generating — "Response must stop generating before deleting." Click **Stop Generating** first, then retry or delete.
</Warning>

## Still stuck?

If Chief reports consistent failures after several retries, [contact the team](/help/help-feedback-whats-new/getting-help-in-chief) at **[support@chief.bot](mailto:support@chief.bot)** with the chat link and roughly when it happened.

## FAQ

<AccordionGroup>
  <Accordion title="I refreshed and the answer is only half written — is the rest lost?">
    Usually not. Re-open the chat — long answers often [finish in the background](/help/chatting-with-chief/running-chats-in-the-background-browser-notifications). If the message still shows as failed or incomplete, click **Try again** to regenerate it in full.
  </Accordion>

  <Accordion title="Why did Chief retry on its own and still fail?">
    When an answer comes back incomplete, Chief automatically re-runs it once or twice. If it still fails, that points to a persistent issue (network, timeout, or credits) rather than a one-off hiccup — check your connection and credit balance, then contact support.
  </Accordion>

  <Accordion title="My prompt says &#x22;Will send when you reconnect&#x22; but nothing happens.">
    That pill means Chief is waiting for your connection to come back. Confirm you're actually online (the offline banner should disappear). If it lingers, click **Cancel** on the pending prompt and send it again.
  </Accordion>
</AccordionGroup>