> ## 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.

# Common issues

<Accordion title="What does the error message 'Return amount is not enough' mean?">
  This error indicates that the expected return amount is below the minimum accepted threshold.
  It typically occurs due to market volatility or low liquidity.
</Accordion>

<Accordion title="What should I do if I encounter the error 'Exchange rate has changed'?">
  This error occurs when the exchange rate changes between quoting and execution.
  You can increase the slippage tolerance to reduce failures, but be aware that it may result in a worse rate.

  For SDK users, implement <code>acceptExchangeRateUpdateHook</code> and return <code>true</code> to automatically accept updated rates.

  See [SDK documentation](/sdk/execute-routes#acceptexchangerateupdatehook)
</Accordion>

<Accordion title="I'm getting an error 'EVM contract destination addresses not currently supported by mayanWH and mayanMCTP'">
  This error means the bridge version you used—mayanWH or mayanMCTP—does not support smart contracts as destination addresses.
</Accordion>

<Accordion title="Why did my Mayan MCTP transfer take so long and cost so much?">
  Mayan MCTP runs on CCTP, which is slower and incurs higher gas costs on Ethereum mainnet.
  This method is typically used for large transfers when other bridges lack liquidity.
</Accordion>

<Accordion title="What does error code 1001: 'None of the available routes could successfully generate a tx' mean?">
  This error often means the <code>fromAddress</code> does not have enough balance to cover the transaction.
</Accordion>

<Accordion title="Why does my bridge show 'Not an EVM Transaction' error even though funds arrived?">
  This error appears when the transaction has not yet been indexed by LI.FI.
  Once it is indexed, the scanner will display the transaction details.
</Accordion>

<a id="eip-7702-delegated-smart-wallets" />

<Accordion title="Why do routes fail for EIP-7702 delegated wallets even when relayer routes are enabled?">
  For EIP-7702 delegated smart wallets, such as delegated MetaMask accounts, gasless or relayer routes are currently not offered, even when <code>useRelayerRoutes: true</code> is enabled.

  In this setup, the Widget may still show regular routes. These routes require the account to hold enough native gas on the source chain, and execution can fail if the account does not have enough gas.

  This behavior is intentional for now because EIP-7702 delegated accounts require a specific signature type, and a generic relayer integration would not be compatible with all smart wallet implementations.

  If your users use EIP-7702 delegated wallets, make sure they hold enough source-chain gas before executing routes. Gasless support for this wallet type is not yet available.
</Accordion>

<Accordion title="What does the error selector 0x963b34a5... mean in a failed swap?">
  This is likely a custom error from the DEX, such as <code>MinimalOutputBalanceViolation</code>.
  Most swap errors originate at the DEX level. If not, LI.FI has fallback validation logic.
  Error selectors vary depending on the DEX.
</Accordion>

<Accordion title="When is a FAILED transaction eligible for a refund, and can its status change afterward?">
  Refund eligibility depends on the bridge or tool used.
  Some bridges refund automatically after failure. Others may leave the transaction unresolved.
</Accordion>

<Accordion title="What does the NOT_PROCESSABLE_REFUND_NEEDED substatus mean?">
  This substatus is triggered by cBridge.
  It indicates the transfer could not be processed due to price, gas, or liquidity changes.
  LI.FI then initiates a refund on the source chain.
</Accordion>

<Accordion title="What does the PARTIAL substatus mean in a transaction?">
  <code>PARTIAL</code> is a final status. The full value was received, but in a different token than expected.
</Accordion>

<Accordion title="What happens if my swap or bridge fails or only completes partially?">
  Same-chain swaps are atomic: they either succeed or revert (gas may still be spent). In cross-chain routes, the bridge can succeed while the destination swap fails; the user is then automatically refunded on the destination chain, typically in the bridged asset. If a destination swap fails, prompt a fresh quote and approval to finish the swap on the destination chain.
</Accordion>