# Archive, export, and troubleshoot

Use this page when a dataset is in the wrong state, a workflow needs a file
snapshot, or an agent cannot access the expected Rowset surface.

For normal dataset creation and row work, start with
[How Rowset datasets work](/docs/datasets) and
[Work with rows](/docs/work-with-rows). This page is for recovery, exports,
and operational checks.

## Archive instead of deleting

Archive mistaken or inactive datasets:

```text
archive_dataset
```

REST:

```http
DELETE https://rowset.lvtd.dev/api/datasets/{dataset_key}
```

Archive keeps rows and schema metadata recoverable, hides the dataset from
normal lists, and disables public preview sharing.

## Restore a dataset

Find archived datasets:

```text
get_archived_datasets
```

Restore one:

```text
restore_dataset
```

REST:

```http
GET https://rowset.lvtd.dev/api/datasets/archived
POST https://rowset.lvtd.dev/api/datasets/{dataset_key}/restore
```

## Export a snapshot

Use exports when another tool expects a file:

```http
GET https://rowset.lvtd.dev/api/datasets/{dataset_key}/export.csv
GET https://rowset.lvtd.dev/api/datasets/{dataset_key}/export.jsonl
GET https://rowset.lvtd.dev/api/datasets/{dataset_key}/export.xlsx
GET https://rowset.lvtd.dev/api/datasets/{dataset_key}/export.sqlite
```

Use MCP row tools for live agent workflows. Use exports for handoff, audit, or
offline processing.

## Common MCP issues

Missing authorization usually means the MCP request is not sending:

```http
Authorization: Bearer YOUR_ROWSET_API_KEY
```

For Codex/OpenClaw-compatible clients, configure the server with:

```bash
codex mcp add rowset --url https://rowset.lvtd.dev/mcp/ --bearer-token-env-var ROWSET_API_KEY
```

Then make sure the agent runtime can read the full `ROWSET_API_KEY`.

If a tool argument fails validation, ask the agent to call
`get_rowset_capabilities` and use live MCP tool discovery before retrying.

## Common dataset issues

- Dataset not found: check that the key belongs to the authenticated Rowset account.
- Dataset archived: restore the dataset before making row or schema changes.
- Row not found: check `row_id` or the configured index value.
- Column not found: call `get_dataset` and compare against current headers.
- Choice value rejected: use one of the configured choice labels.
- Reference value rejected: use a Rowset key or URL owned by the same account.

## Public preview issues

Public previews are read-only. If an agent or script needs data, use MCP or
REST. If a human cannot open the preview, check whether the preview is enabled,
password-protected, or disabled by archiving.