> 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/getting-started/bots-processing-priority.md). # Bots Processing Priority StockHero is a cloud-based stock trading bot platform. This means that at any given time, we are running thousands of processes (the bots) for all our users. In order to ensure an optimal user experience through a responsive trade execution system, we have prioritized the processing of the bots into the following tiers: #### Live Brokerages Premium and Professional Users: Very High Lite Users: Moderate #### StockHero Internal Paper Brokerage Premium and Professional Users: High Lite Users: Low ### What It Mean? If a bot is allocated under the Very High Priority queue, the trade execution is almost instantaneous (barring unforeseen circumstances like network congestion, server downtime, etc.). For users on our Lite plan and trying our Paper exchange, the priority is set to the lowest. This will mean that at times, the bot may miss a trade entry even though the trigger condition is met. For live brokerages, our processing priority is set to be as optimal as possible for users on our Premium and Professional plans. --- # 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/getting-started/bots-processing-priority.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.