---
url: 'https://adk.nht.io/api/@nhtio/adk/shims/variables/E_SHIM_RESOLUTION_FAILED.md'
description: >-
  Thrown when an [`AdkResolverFn`](https://adk.nht.io/api/@nhtio/adk/shims/type-aliases/AdkResolverFn) rejects (or throws synchronously). The
  original failure is preserved on `.cause` so callers can inspect the
  underlying reason (a failed `fetch`, a malformed bundle, a Worker handshake
  that never completed, …); the message additionally embeds its `.message` for
  log lines that only surface the top-level error.
---

# Variable: E\_SHIM\_RESOLUTION\_FAILED

```ts
const E_SHIM_RESOLUTION_FAILED: CreatedException<[string]>;
```

Defined in: [src/shims/index.ts:203](https://github.com/NHTIO/ADK/blob/v1.20260713.1/src/src/shims/index.ts#L203)

Thrown when an [AdkResolverFn](../type-aliases/AdkResolverFn.md) rejects (or throws synchronously). The original failure is
preserved on `.cause` so callers can inspect the underlying reason (a failed `fetch`, a malformed
bundle, a Worker handshake that never completed, …); the message additionally embeds its `.message`
for log lines that only surface the top-level error.

## Remarks

Non-fatal by design: a resolver failure is an environmental/runtime condition (a bad network, a
missing asset, an unregistered ambient resolver), not a programming error, and the memo is cleared
on this path — the very next [AdkShim.resolve](../interfaces/AdkShim.md#resolve) call re-invokes the resolver and can still
succeed. The ambient [adk](adk.md) shim raises this same exception, with a distinct cause message,
when [AdkShim.resolve](../interfaces/AdkShim.md#resolve) is called before any [registerAdkResolver](../functions/registerAdkResolver.md) registration.
