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

# Notebook Troubleshooting

> Resolve notebook access, data, execution, import, and saving problems

## The assistant is missing

Demo accounts do not have assistant features. Other users should open a notebook, expand the right sidebar, and select **Agent**. If another user is editing, wait until the notebook becomes available and click **Edit notebook**. See [Organization Access](https://docs.atomscale.ai/platform/reference/notebooks/saving-and-access.md#organization-access).

## The Analysis uses the wrong data

Give the assistant the intended sample or data item name, ID, time range, and relevant context. Ask it to show which sources it selected before revising the analysis. Check that you are signed in to the intended organization.

## Results are empty or incomplete

Find the source data in **Data Catalog** and check its [pipeline status](https://docs.atomscale.ai/platform/reference/models/data-items.md#pipeline-status). A successful upload does not mean every derived result is ready. Ask the assistant to distinguish missing input, a filter that matches no data, and unavailable processed results.

For gateway data, check [Finding Collected Data](https://docs.atomscale.ai/platform/reference/connecting-data/integrations.md#finding-collected-data). Data without a physical sample may need to be included using the catalog's footer control.

## The notebook opens read-only

Saved results normally open read-only. Click **Edit notebook** when available. If the banner says another user is editing, review saved results while you wait. The saved view does not show their unsaved changes.

If you see source code instead of outputs, the saved-result rendering may still be pending or unavailable. This is separate from an error executing a cell in the editor.

## The session paused or a cell failed

Click **Resume notebook** or **Resume** if the session paused. Inspect the error shown by a failed cell. Check imports, input selection, and any references to files on your own computer, which are not automatically present in the hosted notebook.

Ask the assistant to explain the failure and make a focused correction. Rerun the relevant cells and inspect the results before saving. The SDK is preinstalled; use `Client()` without adding an API key.

## Saving fails

Keep the current editor open and retry **Save Changes** after the connection recovers. Do not switch versions or discard the session while unsaved edits matter. **No changes to save** means the source already matches the saved version; it is not a save failure.

If the problem persists, contact [support](mailto:support@atomscale.ai) with the notebook URL, approximate time, and error text. Do not include credentials.

## Import fails

Use **Upload Existing Notebook** and select one `.py`, `.ipynb`, or `.md` file. The file picker accepts files up to 20 MB, but the converted notebook source has a separate size limit. Split a large investigation into smaller notebooks if its source is rejected.

Read the conversion error. A malformed Jupyter file or damaged marimo structure needs correction before upload. Jupyter outputs and attachments are discarded; imported code may need changes to satisfy marimo cell dependencies or replace unavailable local files and packages.

See [Creating a Notebook](https://docs.atomscale.ai/platform/reference/notebooks.md#upload-an-existing-notebook) for supported formats.


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