# Agent DRONE\_TIMEOUT for stuck builds

**URL:** <https://drone.discourse.group/t/agent-drone-timeout-for-stuck-builds/9250>\
**Category:** Drone Support\
**Created:** [January 18, 2018, 10:38pm UTC](https://drone.discourse.group/t/agent-drone-timeout-for-stuck-builds/9250 "2018-01-18T22:38:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yellowmegaman](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/yellowmegaman/32/3786_2.png) [@yellowmegaman](https://drone.discourse.group/u/yellowmegaman)\
**Post date:** [January 18, 2018, 10:38pm UTC](https://drone.discourse.group/t/agent-drone-timeout-for-stuck-builds/9250/1 "2018-01-18T22:38:55Z")

</div>

Just wondering, if this parameter is still recognized by agent

Added `- DRONE_TIMEOUT=10m` to agent environment, got build that is always stuck (check config template hanging) for more than 10m, and still is not killed.  
No new messages in console, `docker ps` shows it like this:

```auto
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3b893d2a5d6e hashicorp/consul-template:0.19.4-alpine "/bin/sh -c 'echo $C…" 19 minutes ago Up 19 minutes 0_1555278098931671417_step_4

```

And the logs:

```auto
$ docker logs -f 0_1555278098931671417_step_4

```

are showing frozen output, no new lines etc.

Could be terminal is somehow updated still… Or maybe this param should go to server env?