> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/help/support.md). # Troubleshooting and support Keep the game or transaction ID and the date and time. Support needs these details to investigate. ## Game stopped updating Check your connection, then refresh once. Reopen the existing game or result before starting another paid entry. If the result is missing, contact support with the entry details and your last action. A connection problem does not guarantee a refund. A platform-voided cash game refunds the entry. Check the recorded result and refund status. ## Entry charged, result missing Check game history and the status of your entry. Contact support with the game ID, entry charge or reference, and time. Another entry will not recover the missing result. ## Cash prize pending Check the winning result and wallet history. If the credit remains pending, contact support with the game ID, expected prize, and pending-credit reference. ## Deposit missing Check the token, network, destination, and source transaction status. For a bridge transfer, check the provider's status too. A completed bridge can still be waiting for Size wallet credit. Keep the transaction ID and route details. Do not send another deposit to recover it. ## Withdrawal missing Check wallet history for the transfer status, transaction ID, and destination. Contact support about the existing transfer before retrying. ## Funded payout blocked Open positions block payouts. Close all positions on the funded account before requesting. Read the error and check: * The $5 gross minimum. * The available payout amount. * Whether the funded account has breached. * Any required eligibility check. A wallet withdrawal cannot bypass an account's payout limit. ## Contact support Use the in-app bug report. If you cannot sign in or need help with a money issue, open a private ticket in [Size Discord](https://discord.gg/hbQcVVSQ8Q). Include: 1. What you tried and what happened. 2. Date, time, and timezone. 3. Game or transaction ID. 4. Username and relevant screenshots. Never share a password, sign-in code, private key, or seed phrase. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.size.club/docs/help/support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.