A Solana transaction can be valid, signed, and still fail before it changes anything. One common reason is a preflight check: a simulation that a wallet or client asks an RPC node to perform before it broadcasts your signed transaction. Learning what this check can and cannot tell you helps you read wallet errors without assuming that a failed preview means your funds moved.
What preflight does
Solana clients can simulate a transaction against a recent view of blockchain state before sending it to validators. The simulation runs the transaction instructions in order and reports whether they would succeed, along with logs, compute use, and possible errors. Because it happens before normal broadcast, it can catch problems such as an invalid account, insufficient funds, a program error, or a transaction that exceeds its compute limit.
Think of it as a rehearsal, not a reservation. The simulation does not lock your SOL, guarantee a place in a block, or promise that the live transaction will have the same result.
Why simulation and execution can differ
Blockchain state changes continuously. Between simulation and landing, another transaction may spend a balance, update an account, or alter a program-controlled condition. A recent blockhash can also expire while a transaction waits. Network congestion, validator behavior, and a changed account state may therefore make a transaction fail after a successful preflight.
The reverse is possible too: a preflight error is evidence about the simulated state and configuration, but it is not proof that a transaction was broadcast or executed. Check the wallet status and, if you have a signature, inspect that exact signature on a trusted Solana explorer.
Reading common errors
- Insufficient funds: verify the sending account has enough SOL for the transfer and network fee. Token transfers may also require the relevant token account.
- Blockhash not found: the transaction may be too old. Rebuild and approve a fresh transaction in the wallet rather than reusing stale signed data.
- Custom program error: an application instruction rejected its inputs or a program condition. Read the surrounding logs and ask the application team if the meaning is unclear.
- Compute limit exceeded: the instruction sequence needs more compute than allowed. A reputable app may adjust its compute budget; do not blindly approve unexplained changes.
When a wallet offers to proceed
Some clients let users skip preflight or send despite a simulation warning. Doing so removes a useful early warning; it does not fix the underlying issue. Only proceed if you understand the transaction, recognize the application, and can verify the destination and requested token amounts. Never share a recovery phrase or private key with support.
A successful simulation is helpful evidence, not a guarantee. A failed simulation is a warning to investigate, not automatic proof of a completed transfer.
A simple troubleshooting routine
- Read every wallet prompt and confirm the network is Solana.
- Check the transaction accounts, amount, fee, and application before signing.
- If it fails, note the exact error and request a fresh transaction from the trusted app.
- After signing, use the signature to check confirmed status on an explorer; do not retry repeatedly without checking whether an earlier attempt landed.
Preflight checks make many mistakes visible sooner, but they cannot replace careful approval or on-chain verification. Treat them as one safety signal in a broader routine: understand what you sign, protect your keys, and verify outcomes using the transaction signature.