« failed to buy » and « failed to sell »
a failed transaction feels like the app breaking. usually it is the app refusing to give you a terrible price, which is the correct behaviour dressed up as an error.
a failed trade reads like the app breaking. in most cases it is a guard doing its job — refusing to fill you at a price far from the one you were quoted. that is worth internalising before you go looking for a setting to turn it off.
cause 1: the price moved (slippage guard)
the most common by a distance. between the moment you were quoted and the moment the transaction executed, the price moved beyond the slippage tolerance, so the trade reverted instead of filling.
on the tokens fomo traders actually trade, this is not an edge case. these things move 30% in minutes routinely, and if you are trading into a move — which, if you are following an alert, you are by definition — the price is moving against you specifically because other people are doing the same thing.
what to do: retry, and expect a worse quote than the one that failed. if it fails repeatedly, that is a signal about the token's depth and the moment you have chosen, not a bug to defeat.
cause 2: there is not enough of the token to trade
the more serious one, and the one that dominates failed sells.
there is a fundamental asymmetry in thin tokens: entering is easy and exiting is not. when you buy, you are the buyer everyone wants — sellers are delighted. when you sell, you need someone still willing to bid, and on a token that has already made its move there may be very little on that side of the book.
if your position is larger than the available depth, the sell cannot fill within any sane slippage bound. the transaction fails, you try again, it fails again, and it feels like the app has trapped you. the app has not. the liquidity has.
what to do: sell in pieces. a quarter at a time will often clear where the whole position will not, at a worse average price. and treat it as information for next time — position size relative to a token's real depth is a decision made on the way in, which is exactly the argument for a hard per-trade cap.
cause 3: no gas
every transaction costs a fee in the native token of whichever chain it routes through, and fomo routes across several. an account swept to exactly zero cannot pay for its own next transaction, which produces failures that look mysterious because the balance clearly shows funds.
what to do: keep a few dollars of gas per chain, permanently. this is a one-time habit that eliminates an entire class of failure.
cause 4: the token itself will not let you sell
the one worth taking seriously. some tokens are constructed so that selling is restricted, taxed punitively, or possible only for certain addresses — honeypots. the buy works perfectly. the sell never does.
if a token buys fine and consistently fails to sell while others in your wallet sell without issue, stop retrying and start reading the contract. no slippage setting fixes a contract that does not want you to leave.
triage, in order
| symptom | most likely | fix |
|---|---|---|
| fails during a fast move, works later | slippage guard | retry, accept worse quote |
| sells fail, buys work, same token | liquidity — or a honeypot | sell in pieces; check the contract |
| everything fails, all tokens | no gas | fund gas on that chain |
| fails only on one token, always | the contract | stop. do not add. |
| fails across the whole app | not you | see fomo app not working |
the thing the failures are telling you
a token you cannot reliably sell is a token you should not have bought at that size. every copied entry carries an implicit bet that you will be able to leave, and that bet is priced nowhere on the screen.
the durable fix is upstream of the error message: smaller tickets relative to a token's actual depth, a hard cap that overrides your ticket, and exits that do not depend on a stop loss holding on an illiquid asset.
frequently asked
why does fomo say failed to buy?
most often the price moved further than the allowed slippage between quoting and executing, so the transaction reverted rather than filling you at a much worse price. other common causes are insufficient gas on the chain the trade routes through, and a token with too little liquidity to fill your size at any acceptable price.
i keep failing to sell a token. what is happening?
almost always liquidity. entering a thin token is easy because you are the buyer everyone wants; leaving is a negotiation with whoever is still bidding. if the depth on the other side is smaller than your position, the sell cannot fill at a price the slippage guard will accept. selling in smaller pieces usually works, at a worse average price.
should i just raise my slippage tolerance?
carefully, and never as a reflex. raising slippage does not create liquidity, it just widens the price you are willing to accept — and on a thin token it converts a failed trade into a filled one at a price you would have rejected if it had been shown to you plainly. the guard failing is often the system working.
does a failed transaction still cost me money?
a reverted transaction can still consume gas on most chains, because the network did work before hitting the failure. the trading fee itself would not apply to a trade that did not execute. repeated failures on the same token are therefore not free, which is another reason to treat them as information rather than as something to retry harder.
stop reading. start copying.
pick a trader from the fomo leaderboard, set your size, and the entries and the exits land in your own wallet while you sleep.
open copypump on telegram →