While working with Solana, you will encounter various error codes. In this FAQ, we will delve into the realm of Solana API error codes, demystifying their meanings and providing insights into how to handle and troubleshoot them effectively. By understanding these error messages, developers can streamline their debugging processes and ensure the smooth operation of their Solana-powered applications.
| Code | Message | Explanation |
| -32002 | Transaction simulation failed: Error processing Instruction 4: custom program error: 0x26 [41 log messages] | The transaction you're sending has errors, you'll need to double check the params, signature, etc. |
| -32002 |
Transaction simulation failed: Blockhash not found |
That could happen if the blockhash sent in the tx is not known by the validator yet, a retry mechanism is recommended. |
| -32003 | Transaction signature verification failure |
This could be due to an incorrect private key or public key. The signature will become invalid. |
| -32004 | Block not available for slot x |
This error could happen when there's a timeout, a max. X number retry with a few hundred millisecond delay mechanism is recommended. This error could lead to 32007 when slot will eventually get skipped or missed. |
| -32005 |
Node is unhealthy Node is behind by xxxx slots |
You should not see this error often, but this indicates that the node you're reaching is a bit behind the tip. Use the retry mechanism mentioned above. https://support.quicknode.com/hc/en-us/articles/10836747832337-Node-is-behind-by-xxx-slots |
| -32007 |
Slot xxxxxx was skipped, or missing due to ledger jump to recent snapshot |
This happens when you're requesting a block that does not exist. Please check the Solana Block Explorer to verify that. |
| -32009 |
Slot xxxxx was skipped, or missing in long-term storage |
Refer to this FAQ for a deeper explanation https://support.quicknode.com/hc/en-us/articles/5793700679441-Why-are-slots-blocks-missing-on-Solana- |
| -32010 |
TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA excluded from account secondary indexes; this RPC method unavailable for key |
This error is when you send an unexpected payload or not sending the correct data to the Solana validator. See https://support.quicknode.com/hc/en-us/articles/12804627025041 to correctly handle this error |
| -32013 | There is a mismatch in the length of the transaction signature |
The length of the signature is not expected |
| -32014 | The status of the block for the specified slot is not yet available |
This can be either the block is still pending or the node did not sync that specific block yet. A retry mechanism is recommended. |
| -32015 |
Transaction version (0) is not supported by the requesting client. Please try the request again with the following configuration parameter: "maxSupportedTransactionVersion": 0 |
Solana added support for new transaction version types through a concept known as Versioned Transactions. |
| -32016 | Minimum context slot has not been reached |
Double-check when your request is required to be resolved at, could be too far in the future. |
| -32602 | Invalid params: xxxxx |
Double-check the flags/params you've set for the request. Use https://www.quicknode.com/docs/solana as a reference |
There are a couple of errors that are uncommon, you can find them defined here in the official Solana Client Github Repo
If you come across an unknown Solana error, feel free to reach out to the Support team.
Comments
0 comments
Article is closed for comments.