> For the complete documentation index, see [llms.txt](https://docs.whales.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whales.market/pre-market/cross-chain-settlement/failure-scenarios.md).

# Failure Scenarios

#### Bridge Delays

If bridging is delayed:

* Settlement remains pending
* Funds are safe
* Users are notified of the pending state

#### Seller Does Not Bridge

If the seller fails to bridge within the allowed window:

* The order may expire
* Penalty rules may apply

***

### FAQs

<details>

<summary>Your funds stay safe, even during delays</summary>

If bridging is delayed, the settlement remains in a pending state and funds remain secure while users are notified of the status.

</details>

<details>

<summary>Are my funds at risk if a cross-chain message takes longer than expected?</summary>

No, funds are safe during bridge delays, though the settlement will not proceed until the cross-chain message is confirmed.

</details>

<details>

<summary>What occurs if a seller fails to bridge their tokens within the required timeframe?</summary>

If the seller does not complete the bridge step within the allowed window, the order may expire.

</details>

<details>

<summary>Are there consequences for sellers who do not complete the settlement bridge?</summary>

Yes, if a seller fails to bridge the required assets, penalty rules may be applied according to the protocol's terms.

</details>

<details>

<summary>How will I know if my settlement is stuck due to network congestion?</summary>

The system will provide a notification to inform users if their settlement is in a pending state due to bridge delays.

</details>


---

# 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.whales.market/pre-market/cross-chain-settlement/failure-scenarios.md?ask=<question>&goal=<endgoal>
```

`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.