> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/zebratester-scripting/zebratester-user-guide/2.-scripting-the-load-test-session/5.-execution-control-url-loops.md).

# 5. Execution Control - URL Loops

Define URL loops by starting at the Main Menu and the line of the URL that you want to start a URL loop at.

The Add Transaction/Insert Page Break/URL Loop Dialog will appear.

Select the URL Loop Tab:

**URL Loop Input Fields:**

* **Entry Condition**: Create a condition to be satisfied in order to start the loop.
  * An existing Variable can be selected
  * It can be made a mandatory condition based on the value of a variable.
* **URL Loop Description**: The Name of the URL Loop.
* **URL Loop Start Item** and the **URL Loop End Item**: Select the Start and End URL index numbers.
* **Loop Iterations**: Fixed or Variable.
  * If Variable is selected, by clicking on the icon to the right you may create a new Var with a User Input Field
  *

 **Hint: User Input Fields are freely configurable load test program options,**\
**for which you are prompted when starting the load test:**\
**For a User Input Field to take effect, you must assign its variable.**

* Select the **Action if the planned duration of Load Test exceeded**: Action has to be selected for either
  * **Break/Abort** URL Loop after the current iteration
  * **Continue** the loop iterations if the load test item exceeded.
* **Enable Pacing** (Minimum Loop duration per User): Fixed or Variable.


---

# 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.apica.io/platform-docs/zebratester-scripting/zebratester-user-guide/2.-scripting-the-load-test-session/5.-execution-control-url-loops.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.