> For the complete documentation index, see [llms.txt](https://docs.cfdhero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cfdhero.com/getting-started/bots-processing-priority.md). # Bots Processing Priority CFDHero is a cloud-based CFD trading bot platform. This means at any one time we are running thousands of processes (the bots) for all our users. In order to ensure optimal user experience through a responsive trade execution system, we have prioritize the processing of the bots into the following tiers: #### Live Brokerages Premium and Professional Users: High Lite Users: Moderate #### CFDHero Internal Paper Brokerage Premium and Professional Users: High Lite Users: Low ### What It Means? If a bot is allocated under the High Priority queue, the trade execution is almost instantaneous (barring unforeseen circumstances like network congestion, etc). For users on our Lite plan and trying our Paper exchange, the priority is set to be 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 lite plan. --- # 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: ``` GET https://docs.cfdhero.com/getting-started/bots-processing-priority.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.