Jito Bundle Failed? How to Fix It — Complete Troubleshooting Guide

Bundle failed. Token launched without your wallets buying. It's one of the most frustrating experiences in memecoin development. The good news: 90% of bundle failures have simple fixes.

Reason 1: Tip Too Low

The most common cause. During peak hours (2-8pm UTC), Jito validators receive hundreds of bundles per second. Your 0.001 SOL tip gets ignored. Fix: increase priority fee to 0.005-0.01 SOL during busy periods. SolBundler lets you set this before each launch.

Reason 2: Insufficient SOL in Wallets

If any wallet in your bundle has insufficient SOL to cover the buy + fees, the entire bundle fails atomically. Fix: always refresh balances before launching. Each wallet needs buy amount + 0.015 SOL minimum for fees.

Reason 3: RPC/Endpoint Issues

Single-endpoint bundlers fail when that endpoint is down. SolBundler sends your bundle to 5 Jito endpoints simultaneously — NY, Amsterdam, Frankfurt, Tokyo, and mainnet. If one is down, 4 others catch it.

Reason 4: Stale Blockhash

Transactions expire after ~90 seconds. If your bundle takes too long to build (large image upload, slow IPFS), the blockhash expires. Fix: upload your token image in advance using the upload feature, then launch quickly.

Using Reland Bundle

If your bundle failed after token creation (token exists but wallets didn't buy), use the Reland Bundle button in Project Manager. This re-executes the bundle wallets buy without creating a new token.

First Step: Confirm the Bundle Actually Failed

Before troubleshooting, confirm what actually happened. Go to Solscan and search your token's mint address. If the token doesn't exist — the bundle failed completely, including token creation. If the token exists but shows zero buy transactions from your bundle wallets — token creation succeeded but bundle buys failed. If the token exists with some buys but missing others — partial failure. Each scenario requires different response. The most common developer mistake is assuming failure when the bundle is simply delayed — always wait at least 3 minutes before concluding failure.

Fix 1: Increase Jito Tip and Retry

If the bundle was dropped (no transactions on Solscan after 3+ minutes), the most likely cause is an insufficient Jito tip. The fix: increase your tip by 100-200% and submit a new bundle immediately. In SolBundler, update the tip amount in the deployment configuration and click Deploy again. Your wallets still have their SOL since no transactions executed. Do this quickly — if the token creation also failed, you want to relaunch before the narrative window closes. If token creation succeeded but buys failed, act even faster — snipers may be buying while you troubleshoot.

Fix 2: Check and Refund Bundle Wallets

If bundle wallets show no transactions at all but SOL balances are unchanged, the bundle was dropped before submission. Verify each wallet's balance on Solscan — all should show their original funded amount. No SOL was lost. For a complete retry, simply resubmit the bundle with a higher Jito tip. If some wallets show changed balances (partial fee deduction without confirmed buy), there may be a stuck transaction — wait 5 minutes and check again before any action.

Fix 3: Manual Emergency Buys

If the token was created but bundle buys failed, you face a time-critical situation. Snipers are potentially buying while your wallets are empty. Emergency response: immediately buy from each bundle wallet manually using Phantom or Solflare — import each private key (available in SolBundler's wallet manager) and execute buy transactions as fast as possible. Use high priority fees for speed. This is not atomic but it secures your supply before significant sniper accumulation. Act within 60 seconds of detecting the partial failure.

Fix 4: Resolve Blockhash Expiry

If you see a "blockhash not found" error, your bundle transaction was built too long before submission. Solana blockhashes expire after approximately 150 blocks (60 seconds). This typically happens when: you built the bundle but delayed clicking Deploy, the IPFS upload took unusually long, or network issues slowed submission. Fix: simply retry — SolBundler fetches a fresh blockhash at submission time automatically. If using manual scripts, add a blockhash refresh immediately before bundle submission in your code.

Preventing Future Failures

Post-failure checklist for future launches: verify all wallet balances immediately before launching (not 10 minutes before), set Jito tip to 150% of minimum for your time window, check Solana network status before high-stakes launches, use SolBundler's multi-endpoint Jito submission rather than single-endpoint scripts, and keep a dedicated retry reserve (0.02 SOL extra per wallet) for failed bundle scenarios. Implementing these prevents the vast majority of bundle failures.

FAQ

Did I lose SOL when my bundle failed? If the bundle was completely dropped (nothing confirmed), no SOL was lost — it remains in your wallets. If the Jito tip transaction confirmed but bundle buys did not, you may have lost the tip amount (0.002-0.015 SOL). The token creation fee (0.02 SOL) is lost only if the creation transaction confirmed. Check each transaction individually on Solscan to determine exactly what was paid.

Can I get a refund from SolBundler for a failed bundle? SolBundler's 1% platform fee is only charged when the bundle successfully executes. If your bundle failed and no buy transactions confirmed, the platform fee is not charged. Check your SolBundler dashboard for fee transaction confirmation.

What if my bundle keeps failing despite high tips? Persistent failure despite high tips typically indicates a non-tip issue: wallet funding problem (re-verify each wallet has buy amount + 0.005 SOL buffer), bundle size issue (try reducing wallet count to 10 if using 20), or network degradation (check status.solana.com). If all wallets are funded correctly and network is healthy, contact SolBundler support through the dashboard.

Is it worth relaunching the same token after a failed bundle? Depends on timing. If failure and relaunch happen within 5 minutes, most of your narrative window is intact. If the token was created but existed for 30+ minutes with sniper accumulation, community perception may already be negative. Evaluate the on-chain state before deciding — if snipers hold under 10% and the chart isn't catastrophically damaged, relaunch with a corrected bundle is worth attempting.