# Every Terminal Error Message, Decoded (Padre Terminal Troubleshooting)

> Slippage Too Low, Not Enough Funds, Trade Limit Exceeded, Account Frozen. The full Terminal (formerly Padre) error catalog, what each one means, and the fix.

*Source: https://terminalpedia.com/troubleshooting/terminal-error-messages-explained*

Terminal throws a specific, named error when a trade fails. The wording is precise and the errors are genuinely distinguishable from one another, which is more than a lot of trading apps manage.

The problem is that the catalog has never been published anywhere. `docs.padre.gg` went offline around March 2026 and now redirects every path to a login wall, so searching for the exact string you just saw returns nothing useful. Support is a Discord ticket behind an invite. Reddit threads asking about these errors mostly sit unanswered.

So we pulled the error strings out of Terminal's live production JavaScript bundle. What follows is every one of them, verbatim, with what it actually means and what to do.

> **Key takeaway:** Most Terminal failures come down to four things: slippage too tight for the pool, not enough SOL to cover the trade plus its costs, a limit written into the token's own contract, or two of your own orders colliding. Every failure screen carries an error ID. Copy it before you dismiss the dialog, because it is the only thing that makes a support ticket useful.

## The full catalog at a glance

These strings are read directly out of the shipped bundle as of 6 August 2026.

| Error | What Terminal says | Root cause in one line |
|---|---|---|
| Slippage Too Low | "Your slippage tolerance is too low to account for your trade's price impact. Consider retrying with higher slippage." | Your tolerance is narrower than the price move your own order causes. |
| Not Enough Funds | "The transaction could not be completed due to insufficient funds in your trading wallet." | Balance does not cover trade plus fees plus rent. |
| Gas Too Low | "Your gas limit is insufficient to process this transaction. Consider increasing its value." | EVM only. Gas limit set below what the swap needs. |
| Out of Gas | "Transaction ran out of gas during on-chain execution." | EVM only. The gas limit was accepted, then exhausted mid-execution. |
| Transaction Timed Out | "The transaction has failed to complete due to time out." | Never confirmed in time. Three distinct causes, below. |
| Trade Limit Exceeded | "Your trade is likely too big. Check Data & Security for max buy and max sell amounts and adjust your trade size." | The token contract caps order size. |
| Likely Honeypot | "Token might be a honeypot. Always do your research before buying..." | Pre-trade warning. You may not be able to sell. |
| Account Frozen | "The developer of `{token}` froze your account, preventing you from trading this token." | Freeze authority was used against your wallet. |
| Pool Bonded | "Trading on this pool is no longer possible." | The bonding curve completed. Trade the migrated pool. |

Every one of these renders with the same footer: **"Please open a support ticket and provide error ID below"**.

---

## Slippage Too Low

> "Your slippage tolerance is too low to account for your trade's price impact. Consider retrying with higher slippage."

**What it literally means.** Terminal simulated your swap, worked out the execution price you would actually get, and found it outside the tolerance band you authorized. It refused rather than filling you at a price you had not agreed to.

**Why it happens.** Price impact scales with your order size relative to pool depth. A $500 buy into a pool with $10,000 of liquidity moves the price a long way before it fills. Fast-moving launches make it worse, because the curve shifts between quote and confirmation.

**The fix.** Raise slippage on the preset you are actually trading with, in small steps. Slippage lives per preset (Normal, Fast, Ultra and Inferno each carry their own) and buy and sell are configured separately, so changing one number often does nothing at all. If you find yourself pushed above 10% on a routine trade, the honest read is usually that your order is too big for the pool, and the better fix is a smaller order.

**Do not overcorrect.** Cranking slippage to make the error stop is how people end up losing money on every fill instead of failing on some of them. That failure mode is much harder to notice and considerably more expensive, and we wrote it up separately in [why small trades lose money on Terminal](/troubleshooting/terminal-slippage-losing-money).

## Not Enough Funds, and the two ways it shows up

> "The transaction could not be completed due to insufficient funds in your trading wallet."

**What it literally means.** The wallet cannot cover the total cost of the transaction, which is not the same as the trade amount.

**Why it happens.** People consistently underestimate the total. On Solana, one buy costs you the trade amount, Terminal's 1% fee, the bonding-curve or DEX fee, a priority fee (0.001 SOL by default on swaps), a tip (0.0001 to 0.001 SOL by mode, or 0.012 SOL in Inferno), and rent to open a token account for a token you have never held. Set your SOL to "max" and you have left nothing for any of that.

**There are two variants,** and knowing which one you hit tells you where the problem is.

The first is the input-level block, before you ever submit. The amount you typed exceeds the balance, so Terminal will not let the order through. This one is arithmetic and it is your fault. Fix the number.

The second is the post-submit failure above. You had enough for the trade amount but not for the trade plus its costs. This is the frustrating one, because your balance looks sufficient right up until it is not.

**The fix.** Keep a working SOL float that you never trade with. On Solana that means holding back enough for fees and rent on every position you plan to open, not just the current one. If you are down to dust, Terminal will tell you: the app ships the string `Low SOL balance. Swap USDC to SOL` for exactly this case.

> **Warning:** The same problem bites on the way out, and it strands people. A user on r/solana in August 2025 sent USDT into their Terminal wallet, then could not move anything because they had no SOL for gas, hitting "insufficient balance to cover total tx cost". Terminal also enforces `Min. 0.01 SOL required to withdraw`.
> 
> There is no withdrawal troubleshooting page in any version of the documentation. The fix that worked for that user came from another redditor: export the wallet's private key and import it into Phantom, then fund it and move the assets from there. That works because Terminal is non-custodial and your keys are genuinely yours, which we explain in [Terminal wallets and custody](/security/terminal-wallets-custody-private-keys).

## Gas Too Low and Out of Gas

> "Your gas limit is insufficient to process this transaction. Consider increasing its value."

> "Transaction ran out of gas during on-chain execution."

**These are EVM errors.** You will see them on Ethereum, Base, BSC and Robinhood Chain, not on Solana, which has a different fee model. Terminal exposes priority fee in Gwei on EVM chains.

**The difference between them matters.** Gas Too Low is caught before broadcast: the limit you set is visibly below what the swap needs, so nothing is sent. Out of Gas means the transaction was accepted, started executing on-chain, and ran dry partway through. That one costs you the gas consumed and gives you nothing.

**Why it happens.** Token contracts with transfer taxes, reflection mechanics or anti-bot hooks consume far more gas than a plain ERC-20 swap. A limit that works fine for USDC will fail on a tax token. Multi-hop routes cost more than single-hop.

**The fix.** Raise the gas limit on the preset. The gas limit is a ceiling, not a charge: unused gas is refunded, so setting it generously costs you nothing when the transaction is cheap. Repeatedly running out of gas on the same token is a signal about the token, not your settings.

## Transaction Timed Out

> "The transaction has failed to complete due to time out."

This is the least informative message in the set, because it describes a symptom. Terminal's own FAQ gives **three stated causes**, and they are worth memorizing because they cover most cases:

1. **Wallet balance too low to cover the trade plus its cost.** Same underlying problem as Not Enough Funds, surfacing differently depending on where in the pipeline it fails.
2. **Two trades sent at once.** The example the FAQ gives is a limit order triggering in the background while you place a manual trade. If you are running Exit Strategies with up to five take-profit and stop-loss conditions on a position, one of them firing mid-manual-trade will collide.
3. **Slippage exceeded before confirmation.** The price moved outside your tolerance while the transaction was in flight. Same root cause as Slippage Too Low, arriving later in the process.

**The fix depends on which one it is.** Check SOL balance first because it takes five seconds. Then check Open Orders for anything that might have fired. Then look at slippage. If you are on Solana and losing races on volatile tokens, Inferno mode exists for this: it broadcasts the same transaction to bloXroute, NextBlock, Temporal and Jito simultaneously, and a custom program finalizes whichever lands first and discards the rest, so you only pay the tip on the winner.

[Get started](https://terminal.pump.fun/rk/terminalpedia)

## Trade Limit Exceeded

> "Your trade is likely too big. Check Data & Security for max buy and max sell amounts and adjust your trade size."

**What it literally means.** The token's contract enforces a maximum transaction size and you are over it. This is not a Terminal limit, and there is no setting on your side that removes it.

**Why it happens.** Max-transaction caps are common on new launches, sometimes for legitimate anti-sniping reasons and sometimes as a control mechanism the deployer intends to use later.

**The fix.** Terminal already tells you where to look. The Data and Security panel on the token page displays the max buy and max sell values. Size your order under the cap, or split it.

**Read the cap as information.** A very tight max sell with a loose max buy is a shape worth being suspicious about. It means you can get in easily and out slowly, which is a soft version of the honeypot problem below.

## Likely Honeypot

> "Token might be a honeypot. Always do your research before buying..."

**This is a pre-trade warning, not an error.** Terminal will still let you place the trade after you dismiss it.

**What a honeypot is.** A contract you can buy into and cannot sell out of. The sell path is blocked, taxed to nothing, or gated to an allowlist that you are not on. It shows a rising chart the whole time, because buys keep working.

**Where the check comes from.** On EVM chains Terminal integrates `honeypot.is`, plus **EVA Audit**, an AI contract checker that covers **Ethereum and Base only**. There is no contract-simulation equivalent on Solana, so what you get there is the pre-trade data in the next section.

**The fix.** There is no fix. It is a warning about the token, and the correct response is almost always not to buy. If you buy anyway, size it as money you have already decided to lose.

## The other pre-trade warnings

These are not failures. They are things Terminal flags on the token page before you commit, and they are the part of the product that earns its keep.

A freeze authority warning means the mint can still freeze accounts, which is the precondition for the Account Frozen error below. The token tax display shows a buy or sell tax written into the contract, a direct haircut on both legs before slippage even enters the picture. Bundle analysis, dev holding percentage and insider holding percentage tell you how concentrated the supply is, which is your best read on how far the price can fall if one wallet exits. Dev funding source traces where the deployer's SOL came from, and a wallet funded straight from a mixer on a token that launched an hour ago is telling you something. Fresh wallet buys and bot transaction detection separate organic interest from manufactured volume.

None of these block a trade. They are all dismissible. Terminal's position is that you get the data and you make the call.

## Account Frozen

> "The developer of `{token}` froze your account, preventing you from trading this token."

**What it literally means.** On Solana, an SPL token mint can retain a freeze authority. If the deployer never revoked it, they can freeze any individual token account holding that token. Your tokens are still in your wallet. You cannot move them.

**Why it happens.** Sometimes it is targeted at wallets the deployer identifies as bots or snipers. Sometimes it is the exit mechanism for the whole holder base at once.

**The fix.** There is not one. Freezing is a contract-level power, and no trading interface can override it. Only the freeze authority can thaw the account, and by the time this fires they usually have no reason to.

**The prevention is real, though.** Terminal displays the freeze authority warning before you buy. This is the one error in the catalog where the pre-trade warning does the entire job, provided you read it.

## Pool Bonded

> "Trading on this pool is no longer possible."

**What it literally means.** The pump.fun bonding curve for this token has completed and liquidity has migrated. The curve pool you were quoting against no longer accepts trades.

**Why it happens.** You had a stale quote, or a saved position, or a limit order pointed at the pre-migration pool.

**The fix.** Refresh and trade the migrated pool. This is a benign error and often good news about the token: graduation is rare, running at roughly 0.26% of pump.fun launches as of June 2026. Terminal ships a **Raydium Migration Sniper** for exactly this moment, letting you pre-place a buy or sell that fires the instant migration happens, tracked in a Snipes tab.

Post-migration, the fee math changes too. PumpSwap canonical pools use a dynamic rate that starts at 1.25% and steps down to 0.30% as market cap grows. Our [fees guide](/guides/fees/terminal-fees-explained) has the full schedule.

---

## The error ID and the Discord ticket

Every failure in this catalog ends with the same line: **"Please open a support ticket and provide error ID below"**.

That ID is the entire mechanism. Terminal has no email support, no in-app chat, no phone line, and no public issue tracker. A Discord ticket with the error ID is the only way anyone can look at your specific transaction, and a ticket without one is a description of a symptom that support cannot trace.

**Copy the ID before you dismiss the dialog.** It is not stored anywhere you can retrieve it afterward.

> **Warning:** The current app ships `discord.gg/h6ZH2BaYJu`. The older Padre documentation gives `discord.gg/padreapp`. These are different invite codes and we have not been able to confirm they land in the same server.
> 
> **Use the one in the app.** It is the link the current owners are shipping today. Also note that the clone site `padregg.org` advertises `discord.gg/padre`, which matches neither, and is a good illustration of why you should get the invite from inside the product rather than from a search result. More on the lookalike domains in our guide to [Terminal, formerly Padre](/guides/getting-started/terminal-formerly-padre).

## There is no status page, and that is a real gap

If you want to know whether an error is your problem or theirs, you cannot find out.

The public announcement channel at `t.me/s/Padre_Announcements` **stops dead on 15 October 2025**, nine days before pump.fun announced the acquisition, and has not posted since. Before that it did the job properly: it disclosed a primary Solana provider issue in November 2024, Base data lag from a faulty provider in the same month, and a roughly 15 minute Turnkey outage in February 2025 that blocked transaction signing, with the advice to always export your private keys.

That channel going quiet is the single biggest operational regression since the rebrand. Nine months of product changes, two acquisitions and at least two rounds of layoffs have gone by with no public communication channel, no status page and no changelog. The documentation being offline compounds it.

Practically: if several errors fire in a row and nothing about your setup changed, check the Discord before you start changing settings. It is the only place anything gets said.

## Quick triage

| Symptom | Check first | Then |
|---|---|---|
| Same error on every token | SOL balance, then priority fee settings | Discord, since it may not be you |
| Error on one token only | Data and Security panel for that token | Assume the token, not the app |
| Started after you changed a preset | The preset you actually have selected | Slippage and gas limit on that specific preset |
| Only when a limit order is live | Open Orders for a triggered condition | Cancel and retry manually |
| Only on Base | MEV protection, which is unavailable on Base | Widen slippage deliberately for that chain |
| Withdrawal will not go through | SOL balance against the 0.01 SOL minimum | Export the key to Phantom if truly stuck |

---

## The bottom line

The errors themselves are fine. They are specific, correctly worded, and mostly actionable, which puts Terminal ahead of a lot of what it competes with. What is missing is everything around them: no published catalog, no searchable docs, no status page, and a support path that runs through a Discord invite with two versions in circulation.

That gap is why this page exists. If you landed here by pasting an error string into Google, that is the search that should have hit official documentation and did not.

If you are weighing Terminal against the obvious alternative on reliability grounds, our [Terminal vs Axiom comparison](/compare/terminal-vs-axiom) uses cited numbers rather than either side's marketing. And if you are setting up an account, sign up through a referral first: cashback is fixed at signup at 35% instead of 10%, paid in SOL, and cannot be changed later. Details on the [referral page](/referral), or start at [terminal.pump.fun](https://terminal.pump.fun/rk/terminalpedia).

[Get started](https://terminal.pump.fun/rk/terminalpedia)