# Check Stop

URL: https://irs.systems/en/docs/ltt/documentation/ltt-gui-manual/teststand/customsteptypes/checkstop

In your testplan you can place a **LTT Check Stop** check wherever you want. It checks if there is a stop request from the user interface, initiated by the user pressing F1 or F8. If this is the case, the step will **jump to the cleanup section** of the currently executing TestStand sequence.

![Check Stop](/docs/assets/ltt/assets/ts-check-stop.png)

A **check for stop** is necessary to react to **user stop requests** and **TCC value changes**. By default, the only check for stop is done in [MainSequence](/en/docs/ltt/documentation/ltt-gui-manual/teststand/processmodel/orderofexecution). This means:

* The test execution will only stop after an operation mode sequence returns, which can take a long time or not happen at all.
* The testplan can only react to a [TCC value change](../operationmodes/) when the current operation mode is finished.

Both may or may not be desired behavior.

> Be aware that **LTT Check Stop** only jumps to cleanup of the current sequence. If you are in some nested sequence you will need to place a **LTT Check Stop** in each sequence all way up to your [operation mode sequence](../operationmodes/) entry point.

***

* [Read more about other stop criteria](/en/docs/ltt/documentation/ltt-gui-manual/teststand/processmodel/orderofexecution#stop-conditions)
* [Read more about station control](/en/docs/ltt/documentation/ltt-gui-manual/lttgui/stationcontrol)