> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/toolbox/utilities/interval.md).

# Interval

## Introduction

The **Interval Nodes** provide a means for the user to start or reset an **Interval**. An **Interval** is defined by a period of time, in this case a number of seconds. The **Logic** attached to this **Interval** will be repeated over and over every *X* seconds until it is stopped, or reset.

For example, if the **Start Interval** **Node** is triggered, the **Logic** attached to the **Output Pulse Socket** will occur every 5 seconds, assuming 5 seconds is entered in the `Seconds` **Input**. If a **Reset Interval Node** is triggered, the **OnReset Output** of **Start Interval** will be activated and stop the **Interval**, until the user wishes to start it again.

## Contents

* [**Reset Interval**](/incari-studio/toolbox/utilities/interval/resetinterval.md)
* [**Start Interval**](/incari-studio/toolbox/utilities/interval/startinterval.md)


---

# 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.incari.com/incari-studio/toolbox/utilities/interval.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.