# RECORDS_UNKNOWN

> For the complete documentation index, see [llms.txt](https://ensforge.com/llms.txt).

What RECORDS_UNKNOWN means, why MigrationError throws it, what to show users and how to fix it in ensforge. Also covers retry safety.

Source: https://ensforge.com/docs/reference/errors/RECORDS_UNKNOWN

<ErrorMeta errorClass="MigrationError" href="/docs/reference/errors/migration-error" package="@ensforge/sdk" />

## What happened [#what-happened]

The name's records are not known, so they cannot be copied to its new resolver.

## What to show users [#what-to-show-users]

| Title | Message | Action |
| --- | --- | --- |
| Profile needed | The records of This name must be provided before it can be upgraded. |  |

## Retry safety [#retry-safety]

Retrying the same call fails the same way until the cause is fixed (`retryable: false`).

## Actions that throw it [#actions-that-throw-it]

| Action | When |
| --- | --- |
| [`migration.migrate`](/docs/reference/sdk/migration/migrate) | when a name cannot migrate as asked. |

## Catch it [#catch-it]

`Errors.hasCode("RECORDS_UNKNOWN")` narrows to this error. See [Handle errors](/docs/sdk/handle-errors).