> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/sagacli/working-with-chainlet/restarting-a-stopped-chainlet.md).

# Restarting a Stopped Chainlet

As your chainlet runs, it is billed periodically. See the section on [chainlet billing](/sagacli/working-with-chainlet/chainlet-billing.md) to get an understanding of how chainlets are billed, view billing history, export billing history, and other features associated with billing of chainlets.

Should your chainlet run out of funds, it will be halted and it's [status](/sagacli/working-with-chainlet/get-chainlet-information.md) will show offline.

Each chainlet launched is associated with an [escrow account](/sagacli/account-management/view-escrow-account-information.md) into which funds can be added or withdrawn by anyone, at any time. Chainlets are billed by depleting the funds deposited into this escrow account.

If your chainlet displays a status of STATUS\_OFFLINE and your chainlet's escrow account has been depleted, your chainlet can be restarted by [adding funds to the chainlet's escrow account](/sagacli/account-management/deposit-funds-into-escrow.md).

{% hint style="warning" %}
If your chainlet has been stopped due to lack of funds, you will need to [deposit 30 days](/sagacli/working-with-chainlet/chainlet-billing.md) worth of funds in the chainlet's escrow account to enable it to be restarted.
{% endhint %}

Once you deposit the necessary funds in the chainlet's escrow account, your chainlet should restart and show a status of `STATUS_ONLINE`. If you have issues restarting your chainlet, [please contact us](/get-help-and-support.md) for further support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saga.xyz/sagacli/working-with-chainlet/restarting-a-stopped-chainlet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.