THE SHORT VERSION
  • First distinguish a pre-trade refusal, an order still processing and a confirmed failed order.
  • No route, high price impact, slippage and insufficient spendable balance call for different checks.
  • Check the receipt and each wallet's result before submitting a replacement trade.

First: did Cove submit the trade?

A warning before submission is not an on-chain failure. A pending order is not a failed order, either. Open the latest Cove message in the correct profile and read its status, token address, network, selected wallets and reference. If Cove says Previous order still processing, wait and follow that order rather than sending another one.

For a completed market trade, rely on the execution receipt and wallet-level result, not the earlier quote. A multi-wallet action can fill for some wallets and fail for others. Closing Telegram does not cancel an action already processing.

No swap route found

Cove could not find an executable route for that token, size and moment. First verify the token's full address and chain; a ticker alone can point to the wrong asset. Then check whether the panel shows usable liquidity and whether the token is still on a launchpad bonding curve or migrating to a supported pool.

A route can change as markets and providers change. Review a fresh quote later or a smaller amount if that fits your plan, but neither guarantees that the trade will become available. Increasing slippage cannot create a missing route.

High price impact is different from slippage

Price impact is the effect your order has on the available pool price. A large sell relative to thin liquidity can return far less than the position's displayed value. Cove may pause a high-impact trade for another confirmation. Read the expected output and consider whether a smaller size changes the quote; an override can accept a substantially worse result.

Slippage is tolerated movement after the quote. If the market moves beyond the setting, execution may fail. Raising tolerance may permit a worse fill; it does not improve liquidity or fix an unsafe token. Check the active profile's Guardrails and obtain a fresh quote before changing it.

Check spendable balance and trade minimums

A displayed portfolio value is not the same as spendable USDC. Check the selected wallets and their Deployable balance. Funds shown as Parked may need approval in /bridge; Consolidating means the bridge has not finished. In a multi-wallet buy, Split Total and Per Wallet produce different combined spending, and an individual wallet can lack enough funds even when the account total looks sufficient.

Minimum size and token-specific max-buy or transaction limits can also block a trade. Read the amount and any cap in Cove's current message rather than repeatedly sending the same order. Fees and route costs affect what a small trade can execute.

A stale quote or token restriction needs a new decision

If Cove says the quote changed, review the new expected output before another submission. If the token contract blocks transfers, a sell can remain impossible even with enough displayed liquidity. A scam warning or an unverified price is a reason to inspect the token, not a prompt to disable every guardrail.

For a batch, open every wallet result before retrying. Repeating the entire action can buy or sell again in wallets that already succeeded. If the outcome is unclear, preserve the original reference and ask support to trace it rather than treating a missing confirmation as proof of failure.

For a limit, TP or stop order, check whether it is still armed

Open /orders in the profile where you placed the order. Didn't Fire — still active means a high-impact attempt was blocked but the order remains armed. No longer armed, Failed and Expired mean the protection or plan needs a fresh decision. A trigger crossing on a chart is not an execution receipt.

Changing a gas-surplus budget does not recreate a stop that is no longer armed. If creation had an uncertain result, check for an existing order before placing another. Cancel or edit only after confirming the correct profile and order.

When the receipt does not explain the result

Use /support and include the failure message or reference, approximate time, token address, chain, profile and wallet label. Say what you expected and what Cove shows now. This lets support distinguish a pre-order refusal from a submitted order or a wallet-level partial result.

Never send a private key, agent token, seed phrase or wallet-import file to support. Do not submit a replacement trade while an earlier outcome remains unresolved.

KEEP EXPLORING

Sources & further reading

Product settings and availability can change. Check the current documentation before using a feature. Educational content does not predict trading outcomes.

How we approach our content