logo
HOMEFAST TRADING
BLOGDOCS
English
HOME/BLOG/TronLink Swap Failed? Causes and How to Fix It

TronLink Swap Failed? Causes and How to Fix It

liujl2026-11-11 17:53:24

What troubles people most when a token swap fails in TronLink is often not the failure itself. It is not knowing where the money went. The wallet shows one error line. From it you can hardly tell whether the transaction never reached the chain, the contract refused the swap, or execution ran short of energy.

Raising the fee limit or tapping Swap again may not solve it. The first job is to find the step where it broke, and to see what that step consumed.

The causes differ widely in both the fix and the cost. On TRON, energy and bandwidth already spent are not returned, even when no token comes back.

Read the transaction record, and see why the swap failed

Copy the transaction ID from the wallet history and open it in TronScan. Two fields carry the answer: Result, and Energy Usage.

What the record showsWhat actually happenedGo to
TronScan cannot find it, balance unchangedIt never reached the chainCause 1
FAILED, a few thousand energy usedIt executed but missed the swap conditionsCauses 2, 3, 5
FAILED, OUT_OF_ENERGY shownEnergy ran out during executionCause 4

Why not just check the TRX balance? An address that stakes or rents energy can fail a transaction and spend no TRX at all. The energy it used is still gone. An unchanged balance does not mean the attempt was free.

On 11 November 2026 we sampled recent swaps on SunSwap. In one group, 78 of 199 calls failed, close to four in ten. We opened 40 of those failures. Twenty were rejected because the amount received would have fallen below the user’s minimum. Fourteen had an input above the allowed maximum. Six failed in the token transfer itself.

An older group failed differently: 19 of 195 calls ran short of energy, and 6 reverted after execution.

Both kinds carry a resource cost, and the two are nowhere near the same size. The reverted swaps in our sample used 4,070 to 11,983 energy, median 4,149, which is the cheap end. The out-of-energy calls are the expensive kind, and Cause 4 has their numbers. Neither produced a swap.

Before you retry, confirm the signing address holds enough energy and bandwidth. Energy runs the contract, and bandwidth carries the transaction data.

A swap needs more energy than a USDT transfer

A plain USDT transfer moves a token from one address to another. A swap also prices the trade against a pool, checks the conditions, and sends the output token back to you. So it usually costs more energy, and an estimate built for a transfer does not hold here.

In the TronLink mobile app, the swap button opens SUN.io. You are inside TronLink, but the swap is executed by SUN.io’s contracts. The wallet signs. How much energy the swap needs depends on the route it took and on what the contract did.

On 11 November 2026 we measured successful trades on three SunSwap routes. The spread was wide:

RouteSuccessful tradesMedian energyCost if paid in TRX
SunSwap V2 Router121111,43711.14 TRX
SunSwap V3 SwapRouter196164,48216.45 TRX
Earlier V2 router address170182,82818.28 TRX

Those costs are worked out at 100 sun per unit of energy. On the first row, 111,437 energy comes to 11.14 TRX. That is well above the usual energy cost of a USDT transfer. What a USDT transfer costs on TRON against other networks shows how far above.

These are medians from a sample, not a price list. The real figure moves with the route, the state of the pool contract, and the dynamic energy factor.

That is how a 65,000 energy rental fails halfway. Someone sizes the order against the energy a USDT transfer needs, a figure that already doubles with size. The swap runs two-thirds of the way and stops. The rent is paid and the swap is not.

One cost is easy to miss. The first swap of a TRC-20 token may also need an approval, which lets the swap contract spend the tokens in your wallet. It is a second transaction with its own energy bill.

We simulated a USDT approval to the V2 router. It returned 99,764 energy, of which 77,076 came from the dynamic surcharge the network applies to heavily used contracts. At 100 sun per unit, paying that in TRX comes close to 10 TRX.

So before a first swap, price the approval as well as the swap. Check whether the wallet already holds an allowance, since a route that uses Permit2 can change the steps you sign.

Cause 1: the swap never reached the chain

Nothing is charged here, because nothing was mined. The usual reasons:

  • Not enough TRX to pay for bandwidth. A swap in our sample used 539 bytes. Each account gets 600 free points a day, and one swap of that size nearly uses them up, so the rest is paid in TRX. At 1,000 sun per byte, 539 bytes comes to about 0.539 TRX. What TRON bandwidth is and how to get more of it covers the allowance and the ways to top it up.
  • Not enough TRX to cover the resource cost. Energy covers part of the call and TRX covers the rest. If the balance cannot cover the rest, the swap cannot run.
  • The quote expired. The price can move between opening the page and confirming. A quote outside the allowed range is blocked before it is signed.
  • The confirmation came too late. Every transaction carries a deadline. The swaps we checked carried 13 to 58 seconds from creation. One that misses it is dropped, and you have to build a new one.
  • The wallet is on the wrong network or the wrong account. A wallet pointed at a testnet, or an account holding none of the token, cannot complete the swap.

The fix. Confirm the wallet is on TRON mainnet, and that the account holds enough TRX for bandwidth and for any resource shortfall. Then reopen the swap page, take a fresh quote, and sign once. Do not resubmit an expired transaction. Build a new one.

Cause 2: the price moved past your limit

This was the most common failure in our sample. The price you saw when you placed the order differed from the price at execution by more than you allowed, so the swap stopped.

Two messages appear on TronScan:

  • INSUFFICIENT_OUTPUT_AMOUNT: the swap would return less than the minimum you set.
  • EXCESSIVE_INPUT_AMOUNT: the swap would cost more than the maximum you set.

In the 40 failures we opened, those two accounted for 20 and 14.

Two things move the price. A large order of your own pushes along the pool curve, and other trades land first and change the ratio in the pool.

The fix. Take a fresh quote, cut the order size, or move to a pool with deeper liquidity. Do not reach for 5% or 10% slippage on the first failure. A wider tolerance only buys room for a worse fill. It does not add liquidity to a thin pool.

Cause 3: the approval is missing, or it went to another router

If the allowance is zero, or smaller than this swap needs, the swap can fail.

The message is sometimes TRANSFER_FROM_FAILED, which appeared in 6 of the 40 reverts we opened. The same message can come from a token balance that is too low. On its own it does not prove the approval is the problem.

Two details catch people out:

  • A token you have not approved takes two transactions, so the swap has two chances to fail.
  • An approval names one spender contract. A new swap service, or a different route through an aggregator, may ask for a second approval even though you approved the token before.

The fix. Read the contract address the swap page asks you to approve, and confirm it is the one this service uses. Send the approval, wait for it to confirm, then run the swap. If a route you have used before asks again, check the spender address before you sign rather than approving twice.

Cause 4: the swap ran out of energy

OUT_OF_ENERGY means the swap began executing and ran short of energy partway. The swap failed, and the energy and TRX already spent are not returned.

In our sample, the 19 out-of-energy calls reached 672,214 energy used. That is more than three times the median of a successful swap. The TRX burned for energy ran from 0 to 67.22, median 1.96.

Two limits produce this. One is the energy available on the wallet. The other is the fee limit, which caps how much TRX the call may burn. A fee limit set too low stops the call even when the wallet holds TRX.

The fix. Rent or stake energy to the address that sends the transaction, not to the address that receives the tokens. Size it for a swap rather than a transfer. Even 150,000 energy may not be enough on a heavy route, so simulate the swap first and leave a margin. The order is a two-number decision: volume and duration. How TRON energy rental works, and how its price compares with burning TRX covers both, and where the delegation lands.

Cause 5: the token will not let you sell

If buying works and selling keeps failing, the token contract is the likelier cause than your settings. Thin liquidity or a slippage setting that is too tight can produce the same symptom.

  • A transfer tax takes a cut on every move, so the pool receives less than the router checked for, and the swap reverts.
  • A sell restriction lets buys through and blocks sells, often through a blacklist or a trading switch.
  • Thin liquidity cannot absorb the size, and the call returns INSUFFICIENT_LIQUIDITY or a K error.
  • A look-alike contract with the same ticker may have no real pool behind it at all.

The fix. Check the contract address against the project’s own channel, then look at whether sells are restricted and whether the pool is deep enough. If nothing looks wrong, test with a small amount you can afford to lose. No slippage setting and no amount of extra energy fixes a token that blocks sells.

The order to fix it in

This is the order we use ourselves.

  1. Copy the transaction ID and open it in TronScan.
  2. Read Result and Energy Usage, and find the stage where the swap failed.
  3. If no energy was used, check that the transaction reached the chain at all, then check the network, the balance and the bandwidth.
  4. If a few thousand energy were used, read the reason: minimum received, maximum input, or a failed token transfer.
  5. If OUT_OF_ENERGY appears, check the energy on the sending wallet and whether the fee limit is set sensibly. Rent energy if you need it. Before you retry, how to check whether an address holds enough energy shows how to confirm the delivery.
  6. Take a fresh quote before every retry, and never resubmit an expired transaction.
  7. On a token you have not swapped before, check the contract address and test with a small amount.

The habit that costs the most is retrying without reading the cause. Every attempt that reaches the chain spends bandwidth and energy, and a revert gives neither back.

FAQ

Does a failed swap still cost me?

Yes, if it reached the chain. A plain revert used about 4,100 energy and 539 bytes of bandwidth in our sample. Paid in TRX, both come to about 0.95 TRX. Rented energy was paid for in advance and is not charged again, but the energy it covered is gone. A swap that never broadcast costs nothing on-chain.

Why does the same swap work in the morning and fail at night?

Pool prices move, so the same order can miss its limit. Energy demand moves too. The network recalculates it every six hours, and the factor can raise the base requirement to as much as 3.4 times.

Can I swap with USDT only, and no TRX?

You can try, but not reliably. Rented energy covers the contract call. Bandwidth and any remaining shortfall still need TRX, so keep some in the wallet.

Will a higher slippage setting always get it through?

Sometimes. A wide tolerance is the right tool when the pool is deep. If the price genuinely moved a little between quote and confirmation, a slightly worse fill is still a fair trade. It is the wrong tool when the pool is thin or the token takes a transfer tax. There the fill gets worse without getting any more likely.

Does TronLink decide whether the swap succeeds?

No. The swap service quotes the price and builds the route, the contract executes on-chain, and TronLink connects, signs and submits. The reason for a failure sits on the TronScan record.

Sources

  1. TRON chain parameters, queried through the getchainparameters node endpoint on 11 November 2026 (energy 100 sun per unit; bandwidth 1,000 sun per byte; 600 free bandwidth points per account; fee limit ceiling 15,000 TRX; maintenance interval 21,600 seconds, the six-hour recalculation window; dynamic energy enabled with a maximum factor of 34,000, or 3.4 times).
  2. Tronsell.io on-chain sample, 11 November 2026 (200 most recent calls to each of three SunSwap routers; successful calls 121 of 199, 196 of 199 and 170 of 195; median energy 111,437, 164,482 and 182,828; 78 reverts on the current V2 router against 73 on the same router two hours earlier; the 40 reverts we opened split 20, 14 and 6 across the three reason strings; revert energy 4,070 to 11,983, median 4,149; out-of-energy calls burned 0 to 67.22 TRX worth of energy, median 1.96).
  3. SunSwap deployment records in the protocol’s own code repositories (V2 SwapRouter TNJVzGqKBWkJxJB5XYSqGAwUTV15U24pPq and factory TKWJdrQkqHisa1X8HUdHEfREvTzw4pMAaY; V3 SwapRouter TQAvWQpT9H916GckwWDJNhYZvQMkuRL7PN and factory TThJt8zaJzJMhCEScH7zWKnp5buVZqys9x).
  4. SUN.io documentation, how to use SUN.io in the TronLink mobile app (the Swap banner and the Discover entry both open SUN.io, and the two builds differ in which one is shown).
  5. TRON documentation, resource model (0.0001 TRX per unit of energy; bandwidth burn of 1,000 sun per byte; 600 free bandwidth points; a revert deducts only the energy for instructions executed up to the failure, while a crash or timeout deducts all the energy allowed, capped by the fee limit).
  6. TronScan records for the sampled hashes (results REVERT and OUT_OF_ENERGY, the reason strings quoted above, and the energy, bandwidth and burned fee charged for each call).
  7. Node simulation of USDT approve to the V2 router, 11 November 2026 (99,764 energy returned, of which 77,076 was the dynamic-energy penalty).
  8. Sampled swap transactions, expiration minus build timestamp (13.1 to 58.3 seconds; the field is set by the client, not by the chain).

Disclaimer. Figures were checked on 11 November 2026 and will drift. Energy prices are set by committee vote, contract energy requirements are recalculated every six hours, and rental prices move hourly. Verify the numbers before you size a large order. Nothing here is financial advice.

Tags:Swap Errorstron energyTronLink Wallet
←PreviousHow Much TRX to Stake for Bandwidth on TRON (And When It’s Not Worth It)
Next→How to Check If a TRON Address Is Valid Before Sending USDT

More Articles

How to Send USDT From Binance to a TRC20 Address

2026-11-19

How to Send USDT From an Exchange to Your TRON Wallet (and Move It Back)

2026-11-18

How to Check If a USDT Address Is Blacklisted

2026-11-17