> For the complete documentation index, see [llms.txt](https://docs.bogged.finance/bogged-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bogged.finance/bogged-finance/product-information/stop-loss-trailing-stop-loss/stop-loss-faqs.md).

# Stop-loss FAQs

#### How do Bogged DeFi stop-losses work?

When you approve and set a Bogged stop-loss, our systems immediately begin monitoring the price of the token you want to sell. No funds leave your wallet until the target price is reached, which is when Bogged executes the trade from within your wallet.

#### What Chains and DEXes do Bogged stop-losses work on?

Currently, Bogged stop-losses work on BNB Chain, Avalanche, Cronos and Fantom, with further expansion planned for the near future. They can be placed on tokens listed on almost every popular DEX on these chains.

#### Are Bogged stop-losses safe?

With one of the highest volumes of orders placed by any DeFi Limit Order platform, Bogged has become a trusted platform for hundreds of thousands of traders. Fund safety is obviously our highest concern, and we take many serious steps to ensure we the platform and its users remain secure. For more information, [see our articles on security](/bogged-finance/security/overview.md).

#### Why didn't my order fill?

Failed orders are a rare occurrence, but they can happen due to external factors outside of Bogged's control. You should be able to view the reason the order failed in the “my orders” section.

{% hint style="info" %}
If you require further help with a stop-loss, please contact us using the chat bubble on [app.bogged.finance](http://www.app.bogged.finance)
{% endhint %}


---

# 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.bogged.finance/bogged-finance/product-information/stop-loss-trailing-stop-loss/stop-loss-faqs.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.