Why does my GMGN transaction keep failing?

GMGN's own triage order is slippage, then priority fee, then Anti-MEV. Error C1, the most common failure, means your slippage was too low for how fast the price moved. Error A1 means your priority fee was too low and the transaction timed out waiting to be packed. Error A3 means the Anti-MEV RPC service failed, and the fix is to switch Anti-MEV off for that trade. Check those three settings before assuming anything is broken.

Do failed GMGN transactions still cost money?

It depends where the transaction failed. Per GMGN's error documentation, a submission failure in the B1 to B5 range never reaches the chain and costs nothing. An execution failure, error C1, does reach the chain and then reverts, and the same documentation states that this consumes gas and priority fee. GMGN's position is that the money goes to the validator that packed the transaction rather than to GMGN, which is consistent with what a block explorer shows for a reverted transaction, so it is not something support is positioned to refund.

Why can't I sell my token on GMGN?

Error B4 on a sell means the submission was rejected because the token is a Pixiu, the term GMGN uses for a honeypot, or because your address is on the token's blacklist. GMGN's documented answer is blunt: if it is confirmed to be a Pixiu or blacklisted, it cannot be sold. The block sits in the token contract rather than in GMGN, and GMGN's documentation offers no setting that gets around it. Run GMGN's CA Security Checks before buying rather than after.

Why didn't my GMGN limit order trigger when the price hit my level?

Usually error J1. A wick on the chart made it look like your price was reached, but the price never held long enough for the order to trigger on-chain. GMGN's documented position is that a wick basically cannot be triggered, that this is normal, and that it does not need to be solved. The other common cause is J2, where your wallet still looks logged in but the session has silently expired, so nothing fires. Reconnect the wallet to rule that out.

How do I find out why a GMGN transaction failed?

Copy the transaction hash and look it up on Solscan, which is what GMGN's own documentation recommends. The explorer shows whether the transaction reached the chain, what priority fee and tip were actually paid, and the on-chain error. If the failure happened in the Telegram wallet, match the raw error string, such as trade_error_0x1e for a slippage failure, against GMGN's error number table to identify the cause.

TROUBLESHOOTING

Fix It Fast

Transaction failed? Limit order never triggered? Withdrawal sitting there? GMGN publishes an error code for almost every one of these, and this section decodes them.

Reviewed by Concept211, GMGNGuide editorial team|Last verified: August 2026|No user-submitted content. Every code below is checked against GMGN's published error table.

Why Does a GMGN Transaction Fail or Time Out?

GMGN's published error table, read 6 August 2026, sorts trade failures into four families and gives each one a code, which makes diagnosis much faster than guessing.

A1 to A3 are timeouts: priority fee too low, slippage too low for how fast the token is moving, or the anti-MEV RPC failing, and GMGN's own advice for A3 is to turn anti-MEV off.

B1 to B5 never reached the chain at all, most often because you did not keep enough SOL back for gas, which is why GMGN tells users to reserve at least 0.05 SOL.

B4 means the token itself blocked the sale, so a honeypot or a blacklist rather than a settings problem. C1 is the expensive one: the transaction reached the chain, slippage was too low, and the failure still burned your gas and priority fee.

D1 to D3 mean no route was available, whether from the creator pulling liquidity, a launchpad token sitting inside its migration window, or Solana congestion. A timed-out trade may still have landed, so check the chain before you resend.

The step-by-step version is in why your GMGN transaction failed.

Why Does a Limit Order Never Trigger?

The most common complaint here has a boring answer. J1 means the price only touched your level on a wick, and GMGN's published error table lists that as expected behavior rather than a fault.

Beyond that, K1 is a trigger that fired into slippage set too low, K2 is not enough SOL in the wallet when it fired, K3 is not enough tokens to sell, and K4 or K5 mean the token restricted or blacklisted you.

J2 is a stale login, which is worth checking first because the interface can still look signed in. There is also a hard ceiling: error order10008 means you already have 100 active orders, and nothing new will be accepted until you clear some.

Auto-sell has its own trap, since GMGN calculates take-profit and stop-loss per purchase rather than per position, so several buys on the same token leave you with overlapping order sets.

GMGN's recommended settings for automated orders are 30% to 35% slippage and a total on-chain fee of 0.006 SOL or more, higher than the manual-trade defaults for a reason. See the fee and settings guide for how those numbers interact.

Why Is a Withdrawal, Copy Trade or Alert Stuck?

A withdrawal that will not move is usually a lock, not a fault. Withdrawals are web-only, so the Telegram bot cannot send funds at all, and they require Google Authenticator plus a whitelisted destination address.

Changing the whitelist freezes withdrawals for three hours, and re-binding Google Authenticator freezes them for 24 hours.

Copy trading has a quieter failure mode: after three consecutive failed trades the task pauses itself and does not restart, so check the task list if a followed wallet suddenly stopped mirroring.

Missing Telegram alerts usually trace to Telegram's own per-bot rate limits, a plugin wallet that is no longer bound to your Telegram account, or the notification toggle being off.

If you sold and received WSOL instead of SOL, the Solana bot has a one-click converter in its wallet screen. Custody and the documented withdrawal holds are covered in security and custody.

Editorial Standards for This Section

Every troubleshooting page here is written and maintained by Concept211. Error codes and their fixes are quoted from GMGN's published transaction and limit-order failure table, then checked against the live interface, and re-checked when GMGN changes the flow.

This section takes no user-submitted comments, forum threads or community edits.

GMGN's documentation lists no telephone number and routes support through the app, so treat any “GMGN support number” in search results with suspicion, and verify a contact route through GMGN's own site before you use it.

If a step here no longer matches the platform, tell us through the contact page and it gets fixed.

Where Trades Break

GMGN's error table, read 6 Aug 2026

A codesTimeouts

B codesNever submitted

C1Slippage, gas burned

D codesNo route

SOL to reserve0.05 SOL

Trade on GMGN With Code ggguide

Our referral code is ggguide. GMGN pays us a share of the 1% fee you already pay. It gets you no discount and no bonus, and your fee is the same with or without it.

Open GMGN

Troubleshooting12 min

GMGN Transaction Failed: Every Error Code and How to Fix It

GMGN transaction failed? Every published error code from A1 to L3 explained in plain language, with the exact setting to change to make the trade go through.