# TestNet Bugs Troubleshooting We have already identified a number of errors that might interfere with the smoothness of our Testnet workflow, but rest assured, that our Tech development team are working day and night on a solution of these to resolve them as soon as possible. Thus a quick recap of what you might face and how to solve them. Huge thanks to our community who have shared their screenshots and arising troubles with us to build this guide for you! **1) No tokens were received after the Wallet transaction approval.**

From our experience, the simplest solution is:\ \- Click "OK"\ \- Refresh the page, click "Get Tokens" again and try to change the Gas price (GWEI) for the transaction to a value of "25". \ \ The following screenshots will help you to do this correctly, in case you don't know how.

**1 Step: As soon as you sse this pop-up window click "Site Suggested"**

**3 Step: Change both of these values to "25" and after that click "Save" button and proceed with confirming the trnsaction.**

After you have changed your Gas price (GWEI), and Confirmed the transaction, the same error might appear once again. But there is no need to worry, just click the "OK" button once again. The next step is to Refresh the page by clicking our Logo in the top left corner. (Highlighted in the screenshot below)

As soon as the page is refreshed, just wait for a couple of minutes, and your test tokens will appear here (see screenshot).

Now you can make a deposit! --- # 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://frogs.gitbook.io/frogsfi/testnet-tutorial/testnet-bugs-troubleshooting.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.