# CCIP v1.6.0 Aptos Errors API Reference
Source: https://docs.chain.link/ccip/api-reference/aptos/v1.6.0/errors

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

## Errors

### router

Errors that can occur in the main `router` module during a `ccip_send` call.

#### `ccip_send_with_message_id`

| Error Code | Symbol | Description                                                                                                                          |
| ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------ |
|            |        | The provided `dest_chain_selector` does not correspond to a configured and supported destination chain in the router's state.        |
|            |        | The on-ramp version for the specified destination chain is not supported by the current router implementation. The call was aborted. |

### onramp

Errors originating from the `onramp` module, which handles the core logic for sending messages and tokens.

#### `get_fee_internal`

| Error Code | Symbol | Description                                                   |
| ---------- | ------ | ------------------------------------------------------------- |
|            |        | The transfer is blocked by the Risk Management Network (RMN). |

#### `resolve_fungible_asset`

| Error Code | Symbol | Description                                                               |
| ---------- | ------ | ------------------------------------------------------------------------- |
|            |        | The provided token address is not a valid fungible asset metadata object. |

#### `resolve_fungible_store`

| Error Code | Symbol | Description                                                                                                                           |
| ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------- |
|            |        | The provided token store address (or the primary store if `0x0` was passed) is not a valid fungible store object for the given token. |

#### `ccip_send`

| Error Code | Symbol | Description                                                                                                            |
| ---------- | ------ | ---------------------------------------------------------------------------------------------------------------------- |
|            |        | The destination chain configuration for the given `dest_chain_selector` does not exist.                                |
|            |        | The allow-list is enabled for the destination chain, and the caller's address is not in the list of permitted senders. |
|            |        | The token being transferred is not registered with the token admin registry and has no associated token pool.          |
|            |        | The amount of tokens withdrawn from the user's account did not match the expected amount.                              |
|            |        | The fungible asset withdrawn from the user's account does not match the expected asset metadata.                       |
|            |        | An internal consistency check failed; the on-ramp can only be called by its designated router.                         |
|            |        | The number of items in `token_addresses` does not match the number of items in `token_store_addresses`.                |
|            |        | An attempt was made to send a token amount of zero, which is not allowed.                                              |

### fee\_quoter

Errors related to fee calculation and processing of message arguments.

#### `get_token_receiver`

| Error Code | Symbol | Description                                                                                                                 |
| ---------- | ------ | --------------------------------------------------------------------------------------------------------------------------- |
|            |        | The destination chain's family (e.g., EVM, SVM) is unknown or not supported, preventing correct processing of `extra_args`. |

#### `process_message_args`

| Error Code | Symbol | Description                                                                                          |
| ---------- | ------ | ---------------------------------------------------------------------------------------------------- |
|            |        | The calculated fee in Juels exceeds the maximum allowed fee per message configured in the FeeQuoter. |
|            |        | The return data from a token pool's `lockOrBurn` function is larger than the allowed size.           |

### token\_admin\_registry

Errors that occur when interacting with the token registry to manage token pool states.

#### `start_lock_or_burn`

| Error Code | Symbol | Description                                                                                                      |
| ---------- | ------ | ---------------------------------------------------------------------------------------------------------------- |
|            |        | The token pool address is not a valid, registered `TokenPoolRegistration` object.                                |
|            |        | The token pool is not in an idle state and cannot start a new `lockOrBurn` operation because it is already busy. |
|            |        | Internal state inconsistency: The `lock_or_burn_input` storage was expected to be empty but was not.             |
|            |        | Internal state inconsistency: The `lock_or_burn_output` storage was expected to be empty but was not.            |
|            |        | Internal state inconsistency: The `release_or_mint_input` storage was expected to be empty but was not.          |
|            |        | Internal state inconsistency: The `release_or_mint_output` storage was expected to be empty but was not.         |

#### `finish_lock_or_burn`

| Error Code | Symbol | Description                                                                                                              |
| ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------ |
|            |        | An attempt to finish a `lockOrBurn` operation failed because the token pool was not in the correct `LOCK_OR_BURN` state. |
|            |        | The `lockOrBurn` operation could not be completed because the expected output data from the token pool was missing.      |

### token\_admin\_dispatcher

This module dispatches calls to the appropriate token pool.

#### `dispatch_lock_or_burn`

The errors this function can revert with originate from the `token_admin_registry` module during the `start_lock_or_burn` and `finish_lock_or_burn` calls. Refer to the `token_admin_registry` table for a list of possible errors.