> 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/2023.1/toolbox/utilities/interval/startinterval.md).

# Start Interval

## Overview

![The Start Interval Node.](/files/NlcbArDwosf7ObjvhSZM)

The **Start Interval Node** sets an **Interval**, which occurs every *X* `Seconds` (or `Timeout (sec)`). When the **Start Interval Node** fires, the **Logic** connected to the **Output Pulse Socket** will be repeated every *X* seconds. At the same time, **OnStart** is triggered immediately. An **Instance ID** will be created, thus serving as an input for the **Reset Interval Node**. If **Reset Interval** -- connected by the **Instance ID** -- is triggered, **OnReset** fires.

Important to note is that an **Interval** will continue firing until a **Reset Interval Node** is triggered. Without resetting it, it will run forever.

[**Scope**](/incari-studio/2023.1/toolbox/overview.md#scopes): **Project**, **Scene**, **Function**.

## Attributes

![The Start Interval Node Attributes.](/files/YIPywaSZ9JpdPGMgIEHs)

| Attribute       | Type      | Description                                                         |
| --------------- | --------- | ------------------------------------------------------------------- |
| `Timeout (sec)` | **Float** | The time it takes to reach the next occurrence of the **Interval**. |

## Inputs

| Input             | Type      | Description                                                           |
| ----------------- | --------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**. |
| `Seconds`         | **Float** | The time it takes to reach the next occurrence of the **Interval**.   |

## Outputs

| Output             | Type           | Description                                                                                                                            |
| ------------------ | -------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**      | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Instance ID`      | **InstanceID** | The assigned **Instance** of the **Interval**.                                                                                         |
| `OnStart` (►)      | **Pulse**      | Flows to additional actions following **Start Interval** when it starts.                                                               |
| `OnReset` (►)      | **Pulse**      | Flows to additional actions following **Reset Interval** when it is reset.                                                             |

## See Also

* [**Reset Interval**](/incari-studio/2023.1/toolbox/utilities/interval/resetinterval.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/2023.1/toolbox/utilities/interval/startinterval.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.