---
title: "Action interval__start"
description: "Starts an inactivity timer with routing by minutes of waiting."
---

# Action `interval__start`

> **System ID:** `action_interval__start`

## Description

Starts a timer that tracks user inactivity and routes the scenario to branches by minutes of waiting. Thresholds are set via **node connections** (event value = minutes, e.g. `"5"` → after 5 min). If the user writes again — the counter resets. An existing timer for this section is cleared before start.

## Events (scenario branches)

| Event | When it occurs |
|-------|----------------|
| **error** | No parameters or invalid configuration |
| *(numeric branches, e.g. **5**, **10**)* | Inactivity reached N minutes — transition via the node connection |
| *(successful start without a named branch)* | Timer started successfully |

Numeric events are configured on the node outputs in Scenario Builder, not in the JSON parameters.

## Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `type` | string | yes | `"inactive"` | Check type; currently only `"inactive"` is supported |
| `tick` | number | no | `30` | Check interval in **seconds** (lower = more precise) |
| `end` | number | no | auto | Timer lifetime in **minutes**; if not set — from the maximum event |

## Configuration example

```json
{
  "type": "inactive",
  "tick": 30,
  "end": 15
}
```

On the node, add outputs with minute values (e.g. `3` → reminder, `10` → timeout) and connect them to the next blocks.

## Related docs

- [Actions reference](/en/actionjail/reference/actions-reference.md)