> For the complete documentation index, see [llms.txt](https://docs.gofigr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gofigr.io/managed-compute/troubleshooting.md).

# Troubleshooting & FAQ

Common questions and what to do when an instance doesn't behave as expected.

## My instance is stuck in Initializing or Starting services

A cold launch walks through **Launching → Initializing → Starting services → Running** and usually takes 5–10 minutes. The **Initializing** and **Starting services** steps cover first-boot setup and bringing the editors up. Give it a few minutes—we'll email you when it reaches **Running**. If it stays in one step far longer than that, it likely hit an error (below).

## My instance shows an Error

An **Error** status means the machine didn't come up cleanly. The status detail explains where it failed—for example:

* *The instance failed to boot.*
* *Started, but its services didn't come up in time.*
* *Initialization failed.*
* *Stopped after an error.*

Try **Restart…** from the instance menu. If it keeps erroring, contact <support@gofigr.io> with the instance name.

## My instance stopped on its own

That's [idle auto-stop](/managed-compute/lifecycle.md#idle-auto-stop) doing its job—instances stop after a period of inactivity (60 minutes by default) so you don't pay for an idle machine. Nothing is lost; just **Start** it again. To change how long it waits, adjust the idle window under **Auto-shutdown…**.

## I can't connect / the Jupyter button is disabled

The **Jupyter**, **code-server**, and **R Server** buttons only become active once the instance is **Running** and its services are up. If a button is disabled, check the status—if it's still **Initializing** or **Starting services**, wait for **Running**. Connect links are tied to you as the instance owner.

## The Restore action is disabled

You've reached the **3 self-service restore** limit for that instance. Email <support@gofigr.io> to restore it. See [Deleting & restoring](/managed-compute/delete-restore.md).

## Will I lose my files if I stop the instance?

No. Stopping preserves everything on your data volume—notebooks, files, and installed packages. Only **deleting** an instance removes its data. See [Lifecycle & persistence](/managed-compute/lifecycle.md#what-persists).

## How do I avoid surprise charges?

Compute bills per minute only while an instance is **Running**, so **Stop** it when you're done (or rely on idle auto-stop). Storage bills continuously on the data volume even while stopped. Watch your usage on the **Compute Usage** card—see [Compute & storage charges](/billing-and-plans/compute-usage.md).

## Getting help

Still stuck? Email <support@gofigr.io> with your instance name and what you were doing.