> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/customsteptypes/stationstop.md).

# Station Stop

In your testplan you can place a **LTT Station Stop** whenever you want to **actively stop the test execution** of this station. Of all [stop criteria](/ltt/documentation/ltt-gui-manual/teststand/processmodel/orderofexecution.md#STOP_CONDITIONS), this is the only active one, where you, the testplan developer, decide when to stop. That's also the reason why a station stop is usually accompanied with a step precondition.

![TS Req Stop](/files/gbe2LmKXrzje70N2l07f)

Normally, there is rarely a need to actively stop a test from within the testplan. However, if you do so, be aware that the station stop does the same as if a user would have pressed F1 or F8. You still need a [check for stop](/ltt/documentation/ltt-gui-manual/teststand/customsteptypes/checkstop.md) step hierarchy to actually stop the execution.


---

# 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.irs.systems/ltt/documentation/ltt-gui-manual/teststand/customsteptypes/stationstop.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.