# CHAIN_NOT_CONFIGURED

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

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

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

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

## What happened [#what-happened]

The client has no clients for chain ?.

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

| Title | Message | Action |
| --- | --- | --- |
| Network not set up | This app is not set up for that network. |  |

## How to fix [#how-to-fix]

Add chain \<chainId\> to `chains` in Ensforge.create, e.g. `chains: { <chainId>: { publicClient, walletClient } }`.

## 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 |
| --- | --- |
| [`primaryName.set`](/docs/reference/sdk/primary-name/set) | for an L2 that is not in the client's `chains`. |

Any action can fail with `ConfigError`: it is part of `Errors.CommonError`.

## Catch it [#catch-it]

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