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

# Limitations

> Current limitations and constraints of LI.FI Composer when used through the LI.FI API, SDK, and Widget.

These limitations apply to Composer through the LI.FI API, SDK and Widget. Some do not apply to the [Composer API](https://docs.li.fi/composer/composer-api/overview.md), which accepts custom flows.

***

## Current limitations

### Supported EVM chains only

Composer runs only on the EVM chains listed in [Supported Protocols & Chains](https://docs.li.fi/composer/protocols-and-chains.md). Solana, other non-EVM chains and unlisted EVM chains are not supported.

### Tokenised positions only

Composer targets must return a **tokenised position** to the user, such as vault shares, aTokens, liquid staking tokens or yield tokens (Pendle PT/YT, sUSDe). Protocols that return no token on deposit are not supported.

### Deposit-only protocols

Some protocols support deposits but not withdrawals through Composer; users withdraw through the protocol's own interface. In the live [Supported Protocols & Chains](https://docs.li.fi/composer/protocols-and-chains.md) table, a protocol with an `enter-position` edge but no `exit-position` edge is deposit-only.

### Short routes only

The Composer part of a route has at most two hops, and a swap can only be the first hop: for example, a swap followed by a deposit. A target that needs a longer path on one chain (such as two swaps before a deposit) returns no Composer route.

Composer runs on one chain per step. In a cross-chain route, LI.FI adds the bridge: Composer deposits after the bridge on the destination chain, or withdraws before the bridge on the source chain.

### Composer competes with other routes

Composer is not guaranteed to be selected: when a DEX or bridge route into the same token is better, LI.FI returns that route. You can exclude Composer with `denyProtocols=composer`, but you cannot force it. Inspect `includedSteps` to see which route you got. See [API Parameters](https://docs.li.fi/composer/lifi-api/reference/api-parameters.md#filtering-composer-routes).

### IPOR vaults are not available through the LI.FI API

IPOR Fusion vaults are integrated with Composer but cannot be routed through the LI.FI API, SDK or Widget. Quotes into IPOR vaults return no Composer route. To deposit into IPOR vaults, use the [Composer API](https://docs.li.fi/composer/composer-api/overview.md).

### Synchronous positions only

Through the LI.FI API, Composer only uses positions that deliver their output token in the same transaction. Positions whose output arrives later, such as redemptions with a cooldown period, are not routed.

### Composer API features are not available

The LI.FI API runs predefined deposit and withdrawal routes. These Composer API features are not reachable through `GET /v1/quote` or `POST /v1/advanced/routes`:

* Custom multi-step flows authored with the Composer SDK
* [Cross-chain flows](https://docs.li.fi/composer/composer-api/concepts/cross-chain-flows.md): bridge, then run more steps on the destination chain from an escrow

Use the [Composer API](https://docs.li.fi/composer/composer-api/overview.md) for these.

### Cross-chain flows are not fully atomic

A bridge can succeed while the destination deposit does not run. The user then holds the bridged token on the destination chain, and the status is `DONE` with substatus `PARTIAL`. Always poll status and handle `PARTIAL` in your UI; see [Partial failure handling](https://docs.li.fi/composer/lifi-api/guides/cross-chain-compose.md#partial-failure-handling).

### Simulation cannot prevent every revert

Onchain state can change between the quote's simulation and execution (for example front-running, or a vault becoming full), so a transaction can still revert. For a same-chain route the source tokens stay in the user's wallet, but the gas is spent. See [Error Handling](https://docs.li.fi/composer/lifi-api/reference/error-handling.md#onchain-transaction-revert).


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