---
name: "triggerTimeoutCurrent"
type: command
status: ok
groups: ["Triggers"]
arma3_since: "1.08"
locality: {"argument": "global", "effect": null, "server_exec": false}
source: https://community.bistudio.com/wiki/triggerTimeoutCurrent
revid: 376123
updated: 2025-09-01T08:15:52Z
---

# triggerTimeoutCurrent

*Command · Triggers · Arma 3 v1.08*

Locality: arguments **global**

## Description

Returns current timeout of the given trigger or -1 if countdown is not in progress.

> [!IMPORTANT]
> The trigger could be [local](../topics/Multiplayer_Scripting.md#locality) or remote but the result returned by this command will be for the current trigger timeout local to the client that executed the command.
> See [createTrigger](../commands/createTrigger.md) for more info.

## Syntax

```sqf
triggerTimeoutCurrent trigger
```

**Parameters:**

- `trigger`: [Object](../topics/Object.md) - trigger object

**Returns:** [Number](../topics/Number.md) - time remaining before trigger activation.

## Examples

### Example 1

```sqf
_remaining = triggerTimeoutCurrent _trigger;
```

## See also

[triggerTimeout](../commands/triggerTimeout.md) · [setTriggerTimeout](../commands/setTriggerTimeout.md) · [waypointTimeoutCurrent](../commands/waypointTimeoutCurrent.md)

## Community notes

**Killzone_Kid** — 2013-11-26

Triggers have their own schedule. If you create a trigger with timeout and try to read [triggerTimeoutCurrent](../commands/triggerTimeoutCurrent.md) immediately it will return -1.
This is because the countdown will not start until the next scheduled trigger check is due, and this could take up to 0.5 seconds.

<sub>Source: [BI Community Wiki — triggerTimeoutCurrent](https://community.bistudio.com/wiki/triggerTimeoutCurrent) (revision 376123).</sub>