> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/workflow/stop.md). # Stop Stop is an action used to immediately halt the currently running script at that position. > 📌 Note about scope: This action only affects the termination of the running thread of the current profile, without impacting other threads or profiles running concurrently in the same operation. This action is often combined within an If conditional block to handle critical errors, errors that cannot continue the script, or when the thread has completed its main task. #### Real-world example: Stop the thread when the account is at Checkpoint Suppose you are scripting to manage accounts. When you open the browser, if it detects that the account has been locked (Checkpoint), then performing subsequent actions such as scrolling through posts, liking, messaging... is completely pointless and wastes machine resources. * Configuration steps: * Use an If block to check for the appearance of the error message: `If the text "Account is locked" appears`. * Inside this If block, you call the Stop action. * Result: When the system scans and detects the account is locked, it will encounter the Stop command and immediately close that profile's thread. Other profiles in different threads will continue to run normally without being affected. --- # 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.gpmautomate.com/automate-en/action-guide/workflow/stop.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.