> 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/cyclestartend.md).

# Cycle Start / End

The **LTT Cycle Start** and **LTT Cycle End** step types should be placed at the setup / cleanup of each operation mode sequence. That way the cycle counter will increment by one each time the operation mode sequence has passed through.

Of course, when the cycle counter should increment depends on your concrete testplan. For example, if your operation mode sequence never leaves (not recommended) the cycle end call should be placed inside the loop of your operation mode.

![Cycle Start / End](/files/75ZxCMXr72Ea9eJXYwdd)

The cycle counter is available as a [TestStand variable](/ltt/documentation/ltt-gui-manual/teststand/predefinedvariables.md): **FileGlobals.LTT.RV.Cycles**.

The cycle counter is also added as a separate [history column](/ltt/documentation/ltt-gui-manual/configuration/historyconfiguration.md) per default.

{% hint style="info" %}
Only **cycle end** is needed to increment the cycle counter. You only need to place a **cycle start** step at the beginning of your cycle if you configure **data recording** to **record every x minutes**. [Read more about data recording](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/datarecording.md).
{% endhint %}


---

# 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/cyclestartend.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.