> For the complete documentation index, see [llms.txt](https://docs.stonkfun.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonkfun.bot/understanding-the-system/failures-and-recovery.md). # Failures & Recovery ## A failed action is never shown as successful Success is reported only once the chain confirms it. If something didn't go through, you're told that — not left to assume it worked. ## Ambiguous outcomes are handled conservatively Sometimes it genuinely can't be told, right away, whether a submitted transaction landed. When that happens, STONKFUNBOT doesn't guess in either direction. It doesn't tell you it worked when it isn't sure, and it doesn't resend a transaction that might already have gone through. * **A confirmed transaction is never resent** just because later bookkeeping failed. * **Recovery never re-signs or resubmits on your behalf** — doing so risks paying twice. * **An uncertain result is checked against the chain directly**, rather than assumed either way. Depending on what's actually known about your specific action, you may be told to wait, or that it's safe to try again. Those are treated as genuinely different cases, on purpose — not interchangeable outcomes. ## What no fee is charged for If a launch doesn't succeed, you are not charged STONKFUNBOT's service fee for it. ## What to do if something seems stuck See [Troubleshooting](/help/troubleshooting.md) for what specific messages mean and what to do about them. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.stonkfun.bot/understanding-the-system/failures-and-recovery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.