Documentation for agents: an index at /llms.txt, every docs page in one file at /llms-full.txt, and Markdown for any docs page by adding .md to its URL.

Skip to Content
ensforge

RESOLVER_NOT_FOUND

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

NotFoundErrorNot retryable
@ensforge/sdk

What happened

The name has no resolver.

What to show users

TitleMessageAction
No resolverThis name is not set up to hold records yet.Set a resolver first.

How to fix

Set one with resolver.set.

Retry safety

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

Actions that throw it

ActionWhen
approval.getDelegatewhen the name has no resolver.
approval.setDelegatewhen the name has no resolver.
dns.setRecordswhen the name has no resolver.
permission.setRecordAccesswhen the name has no resolver.
record.getwith strict when the name has no resolver.
record.getAddresswith strict.
record.getAvatarwith strict.
record.getContentHashwith strict.
record.getTextwith strict.
record.setwhen the name has no resolver of its own.
resolver.getwith strict when nothing resolves the name.
resolver.getLinkwithout a resolver, or with strict and no records.
resolver.linkwhen the name has no resolver of its own.
resolver.resolvewhen nothing resolves the name.
resolver.upgradewhen the name has no resolver of its own.
role.getwhen the name has no resolver.

Catch it

Errors.hasCode("RESOLVER_NOT_FOUND") narrows to this error. See Handle errors.

Was this page helpful?