# Debugging Errors We provide our service via clusters of redundant RPC nodes across Europe, America and Asia in order to guarantee maximum transaction success rate. However if a transaction fails to get picked u by the leader you might get error:\ ❌ Failed to execute transaction \ Error: The signature provided is invalid or incorrect. Please check and try again with the correct signature.\ \ This is **TransactionExpiredBlockheightExceededError:** The Signature of the transaction has expired and the block height exceeded you should retry your transaction, as it was not picked up by the block leader.\ \ If you get this error, you wont know because we have added automatic retry function which will ensure your transaction get trough anyways, however this can slow the process with additional 6 seconds, so if you are trading memecoins (sniping) we suggest to cancel teh operation with the `/cancel` command and cast the transaction again.\ \ If you get error code 6014 this indicates problem with the adjusting of your slippage in the settings, you might want to increase your slippage tolerance. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hashhunter.ai/hash-hunter-telegram-bot/debugging-errors.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.