> For the complete documentation index, see [llms.txt](https://docs.stockhero.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stockhero.ai/bot-settings/entry-exit-conditions.md). # Entry / Exit Conditions ### Entry Conditions The bot can only evaluate data if at least one entry condition is set. Multiple entry conditions can be set at a time. A user can also configure one or multiple [TradingView](/technical-indicators/tradingview.md) signals for its Entry Conditions. ### Exit Conditions Similar to Entry Conditions, at least one Exit Condition must be set. The technical indicators set for Exit Conditions need not be the same as those set in Entry Conditions. In Exit Conditions there are two settings that will be prioritized above all Technical Indicators: Stoploss and Take Profit. This means that if the Take Profit condition is met but your exit technical indicator has not been triggered, a market sell order will be executed. However, if the technical indicator trigger is met, the bot will also exit (closing the deal), disregarding your Take Profit or Stop Loss condition. --- # 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.stockhero.ai/bot-settings/entry-exit-conditions.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.