Docs menu
SolBundle Docs

Troubleshooting

What to do when a bundle doesn't land, a wallet is short of SOL, a transfer hits the rent minimum or a confirmation times out.

The messages below are the ones SolBundle actually shows. Find yours, check what it means, and follow the fix.

The launch bundle didn't land

The log ends with Not confirmed within time budget. and the result card shows the mint address without the green success banner. The bundle was re-sent for up to 40 seconds without being confirmed. Usually the network was busy and other bundles outbid it for block space.

Check before you retry
The same signed bundle can still land a little later. Open the mint on Solscan from the result card (or look up your dev wallet) before launching again. A new launch always creates a new token with a new mint address.

Related messages:

  • All bundle submission attempts failed before any were accepted. No Jito region accepted the bundle, so nothing was sent and nothing was spent. Try again in a moment.
  • Failed to get Jito tip accounts. SolBundle couldn't reach Jito. Nothing was sent; try again.
  • Landed but failed on-chain in the log: the creation transaction was included but failed. Check the transaction on Solscan for the reason.

If the launch bundle doesn't land, no snipe buys are sent and the dev and bundle wallets keep their SOL. Only the metadata upload has happened.

A snipe wallet shows "Timed out"

Its buy was not confirmed within its window (up to 20 seconds of resends, then a short wait). It may still have landed a moment later: check that wallet on Solscan, or load the token in the Terminal to see which wallets hold it. Other snipe wallets and the launch itself are not affected.

"Not enough SOL"

When launching

Not enough SOL: Dev wallet has 0.0200, needs ~0.1315; ... means the pre-flight check found wallets that can't cover their buy, the 0.5% fee and their buffer. Nothing was uploaded or sent. Fund the listed wallets with the Fund panel in the wizard (steps 2, 4 and 5) or on the Wallets page, then launch again. The numbers per role are on PumpFun launch.

  • If you used Max or Max all for a buy amount, the wallet is about 0.5% of the amount short because Max leaves room for the buffer but not the fee. Lower the amount slightly.
  • balance unreadable, try again means the balance couldn't be read from the network. Wait a moment and launch again.
  • Launch Token is greyed out with a red note above it when the wizard already knows a wallet is short.

When withdrawing

Not enough SOL: has X, needs Y incl. fee. An exact-amount withdrawal also pays a small network and priority fee (about 0.000025 SOL). Send a little less, or use Max, which takes the fee into account.

When funding

Source wallet doesn't have enough SOL... appears and the Fund button is disabled when the source can't cover the total. Lower the amounts, pick fewer wallets or choose another source.

Rent-minimum errors

Solana rejects any transfer that would leave an account with a balance above 0 but below the rent minimum (about 0.00089 SOL), and won't create a new account with less than that.

  • That would leave 0.000400 SOL - below Solana's rent minimum. Send a bit less, or use Max. Either leave at least 0.00089 SOL behind, or send everything with Max (the wallet ends at exactly 0).
  • An empty address can't receive less than 0.00089 SOL (rent minimum). The destination has never held SOL. Send at least 0.00089 SOL.
  • Funding a brand-new wallet with less than 0.00089 SOL fails the whole transaction it is in (up to 8 transfers). Fund new wallets with at least that much.

"Not confirmed in time"

Not confirmed in time (signature) - check it on Solscan before retrying. The transaction was sent but its confirmation didn't arrive before its blockhash expired. This can happen on Fund, Collect, Withdraw and Terminal buys and sells.

Don't retry blindly
Search the signature on Solscan first. If it succeeded, the transfer or trade already happened and retrying would do it a second time. If Solscan doesn't find it, it didn't land and it is safe to retry. Then press Refresh on the Wallets page to see the current balances.

When funding many wallets, transfers go out 8 per transaction. If one transaction fails or times out, the ones after it are not sent. The result list shows which wallets were funded and which were not.

A wallet can't be deleted

Withdraw or collect first ... Wallet 3 still holds 0.0500 SOL. Deleting is refused while a wallet holds more than 0.0001 SOL, on mainnet or devnet (the message then ends in (devnet)). Collect it or withdraw with Max, then delete.

  • couldn't check its balance right now: the balance couldn't be read, so the delete was refused to be safe. Try again shortly.
  • Tokens are not checked. Before deleting a wallet that may still hold tokens, sell them or reveal and save the private key.

Other launch errors

  • The same wallet is selected in more than one place. Each wallet can be the dev wallet, a bundle wallet or a snipe wallet, but only one of them per launch.
  • Too many bundle wallets (max 3 per launch). / Too many snipe wallets (max 50 per launch).
  • Missing required fields: the name, symbol, image or dev wallet is missing. Go back to steps 1 and 2.
  • Every bundle and snipe wallet needs a positive SOL amount. A selected wallet has an empty, zero or over-100 SOL amount.

Balances show "—"

The balance couldn't be read from the network at that moment. Click Refresh on the Wallets page or reload the wizard.