> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/developers/failure-modes.md). # Failure modes | Situation | Effect | Recovery | | ---------------------------------------- | ---------------------------------------- | ------------------------------------------------------------- | | Launch preparation fails | No signed chain action | Correct inputs and prepare again | | Launch transaction reverts | No launch transition; gas may be spent | Inspect revert and retry with a fresh quote | | Commitment exceeds a limit | Commitment reverts | Use the launch-specific allowed amount | | Automatic launch finalization is delayed | The market remains in its pre-live state | Anyone may finalize after the grace period | | Settlement protections fail | Market must not launch on worse terms | Use defined recovery; delayed cancellation only when eligible | | RPC unavailable | Reads/writes may be delayed | Switch to a verified configured endpoint | | Indexer delayed | UI can be stale | Verify explorer/contract; reconciliation catches up | | Trade slippage/deadline fails | Swap reverts; gas may be spent | Request a new quote | | Fee collection delayed | Accrual is not dispatched yet | Permissionless collection when minimum is met | | Epoch finalization delayed | Claims unavailable | Wait for the published epoch result | | Merkle claim fails | No transfer | Verify wallet, chain, epoch, amount, proof, and claim state | | X disconnected | Future attribution may stop | Reconnect before the attribution deadline | | Partner/referral expires | No new eligible earnings | Accrued claims follow their contract | | Proposal cannot execute | No policy change | Check outcome, veto, timing, and action bounds | | Classification unavailable | Discovery metadata is stale | Market and chain continue operating | Never “recover” by sending funds directly to an address from a support message. Use only contract-backed actions exposed by a verified Souless client. --- # 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://docs.souless.fun/developers/failure-modes.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.