# Wait

Node type `browser_waitTime`

## What it does

Pause the flow between steps for a fixed or random duration.

## Desktop client configuration

![Wait configuration in the desktop client](/assets/wait-time.baeb9488957584671d844e83fb78621cd781fe391578aa8f14ad3d32ec4be64b.0538f3a9.webp)

Captured in the English interface of MoreLogin Desktop V2.73.101.

## Inputs

These fields belong in `data.browserUi.inputs`.

| Field | Type or values | Schema required | Execution default | Description and bounds |
|  --- | --- | --- | --- | --- |
| `timeoutType` | `"fixed"` / `"randomInterval"` (supports variable references) | No | `"fixed"` | Wait mode. Editor initial value `"fixed"` |
| `timeout` | `WorkflowNumber` | No | `1000` | Wait time (ms); minimum after resolution: 0. Editor initial value `1000` |
| `timeoutMin` | `WorkflowNumber` | No | — | Minimum time (ms); minimum after resolution: 0 |
| `timeoutMax` | `WorkflowNumber` | No | — | Maximum time (ms); minimum after resolution: 0 |


## Mode requirements and limits

**`timeoutType` `eq` `"fixed"`**

- After resolution, timeout is a finite number in 0…2147483647, in milliseconds.
- Validation code `RPA_NODE_INPUT_INVALID`


**`timeoutType` `eq` `"randomInterval"`**

- timeoutMin/timeoutMax are numbers in 0…2147483647 and can be fractional; timeoutMin <= timeoutMax. The wait time is timeoutMin + floor(random × (timeoutMax − timeoutMin + 1)). When both ends are integers, this is a uniformly random integer in the closed interval. With fractions, the step is 1, and the result can exceed timeoutMax by less than 1 millisecond.
- Validation code `RPA_NODE_INPUT_INVALID`
- For fixed, timeout defaults to 1000ms. For randomInterval, the default is [1000,3000]ms, and timeoutMin ≤ timeoutMax.
- Validation code `RPA_NODE_INPUT_INVALID`


**`timeoutType` `eq` `"randomInterval"`**

- Required `timeoutMin`, `timeoutMax`
- This field is required in the editor and has no default. If it is omitted, writes and validation return RPA_NODE_INPUT_INVALID (reason=required), and a run is rejected the same way before it starts.
- Validation code `RPA_NODE_INPUT_INVALID`


## Input references

| Field | Allowed forms |
|  --- | --- |
| `timeoutType` | `literal`, `template` |
| `timeout` | `literal`, `numericExpression` |
| `timeoutMin` | `literal`, `numericExpression` |
| `timeoutMax` | `literal`, `numericExpression` |


## Outputs

| Output field | Type or values |
|  --- | --- |
| `waitedMs` | `number` |
| `requestedMs` | `number` |


Reference published fields as `${nodeId.data.field}`.

## JSON example

This example waits a random 1 to 3 seconds. Place the node between the two steps that need a pause.

```json
{
  "id": "pause",
  "type": "browser_waitTime",
  "data": {
    "title": "Pause between 1 and 3 seconds",
    "browserAction": "waitTime",
    "browserUi": {
      "inputs": {
        "timeoutType": "randomInterval",
        "timeoutMin": 1000,
        "timeoutMax": 3000
      },
      "exception": {
        "timeout": 30000,
        "policy": "interrupt"
      }
    }
  }
}
```

[Back to the node catalog](/browser-rpa/nodes)