> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cowboy.inc/llms.txt
> Use this file to discover all available pages before exploring further.

# E1737 — Unresolved import

> Unresolved import

# E1737 — Unresolved import

| Property | Value |
| - | - |
| **Code** | `1737` |
| **Slug** | `E1737` |
| **Category** | `validation` (Validation) |
| **CIP** | CIP-26 §3.4 |

## What happened

Unresolved import: \{name}.

This is the receipt's `what` text, produced by the node's `ExecutionError::UnresolvedImport`. Placeholders in braces are filled from the failing transaction.

## Why it happened

The node rejected the operation with `E1737` (category `validation`, Validation). The receipt's `why` field carries the specific cause and `context` carries structured details, such as the values that filled the placeholders above.

The normative rule is in CIP-26 §3.4.

## How to fix

Publish the missing library under the deploying account, or fix the import name — every candidate import must resolve to a library the deployer owns.

## Receipt example

```json theme={null}
{
  "code": 1737,
  "slug": "E1737",
  "category": "validation",
  "what": "unresolved import: {name}",
  "fix": "Publish the missing library under the deploying account, or fix the import name — every candidate import must resolve to a library the deployer owns.",
  "docs_url": "https://docs.cowboy.inc/errors/E1737"
}
```

***

> [card] [All Error Codes](https://docs.cowboy.inc/errors/overview.md)
>
> View the complete error code reference


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.