Troubleshoot an operation
Resolve unclear status, failed swaps, inactive positions, and leftover fee claims without repeating an operation blindly.
Start with the operation's signature, network, pool, and wallet. Separate what the application prepared, what the wallet signed, what was submitted, and what the network confirmed. Those stages describe different outcomes.
A transaction is pending or missing
Check the original signature through the integration's status view or a compatible explorer on the correct network. An RPC timeout means the response is missing; it does not prove the transaction failed.
If the transaction expired without landing, the application must prepare a fresh one and request new signatures. If the result remains unknown, resolve that uncertainty before repeating a deposit, swap, or claim. A second valid transaction can execute the operation again.
A swap failed
| Reported cause | What to review next |
|---|---|
| Minimum output or maximum input exceeded | Refresh the estimate and review market movement and your chosen bounds |
| Price limit or insufficient liquidity | Check available depth for your amount and direction |
| Insufficient token balance | Check the actual mint and spendable token account, including WSOL where applicable |
| Insufficient SOL | Review the network fee and account deposits in addition to the token budget |
| Hook or eligibility rejection | Read the policy, required proof, and supported wallet context |
| Oversized transaction | The integration may need valid ALTs or a redesigned explicit sequence |
Do not remove limits merely to make a failure disappear. A different pool can have different fees and hook rules, so review any replacement operation from the beginning.
A position is not earning fees
Check whether the position is funded and its range is active. An empty account earns nothing, and an out-of-range position does not participate until trading reaches its interval. Pool-wide volume is not evidence that your range was crossed.
Next, check the pool's LP allocation and whether the display includes fee growth since the last checkpoint. Keep principal changes separate from fee income. See Collect your fees.
Withdrawal left tokens or the position will not close
A normal withdrawal returns the current token mix, which can differ from the deposit. Removing all liquidity can leave unclaimed fees. Closure requires zero liquidity and cleared fee balances, and refunds only the eligible position account's deposit.
If a one-asset exit failed, its conversion may lack liquidity or violate a hook or execution limit. An ordinary two-asset withdrawal has different semantics; review it as a new operation.
Information to retain for support
Keep the public transaction signature, pool and mint addresses, intended action, timestamp, displayed error, and application version where available. Do not share seed phrases, private keys, API secrets, or wallet recovery material.
The security model and known limitations explain integration boundaries. A confirmed result and reconciled balances are stronger evidence than a success toast alone.