Unable to set `script_execution_timeout` agent option from Fleet UI

[wolveix]

Fleet version: 4.60.0

Web browser and operating system: Chrome 131.0.6778.86 running on macOS

---

💥  Actual behavior

I expected to be able to modify the script_execution_timeout agent setting according to https://fleetdm.com/docs/configuration/agent-configuration#update-agent-options-in-fleet-ui

This is an hour-old installation, running with the Docker Compose below:

services:

  caddy:
    container_name: caddy
    image: 'caddy:alpine'
    ports:
      - '80:80'
      - '443:443'
    environment:
      - ACME_AGREE=true
      - CADDYPATH=/etc/caddycerts
    volumes:
      - './caddy/caddyfile:/etc/caddy/Caddyfile'
      - './caddy/config:/config'
      - './caddy/data:/data'
    restart: unless-stopped

  mysql:
    container_name: mysql
    image: 'mysql:latest'
    volumes:
      - './mysql/data:/var/lib/mysql'
    env_file: mysql/default.env
    cap_add:
      - SYS_NICE
    restart: unless-stopped

  redis:
    container_name: redis
    image: 'redis:latest'
    restart: unless-stopped

  fleet:
    container_name: fleet
    image: 'fleetdm/fleet:latest'
    depends_on:
      - mysql
      - redis
    command: sh -c "/usr/bin/fleet prepare db --no-prompt && /usr/bin/fleet serve"
    env_file: fleet/default.env
    volumes:
      - './fleet:/fleet/'
      - './fleet/logs:/logs'
      - './fleet/vulndb:/vulndb'
    restart: unless-stopped

🧑‍💻  Steps to reproduce

1. Navigate to /settings/organization/agents
2. Add script_execution_timeout: 1800 just below the options key in the agent YAML options
3. Click save

🕯️ More info (optional)

I did read the warning in the overview section for the agent configuration, though noted that the script_execution_timeout field in particular should work fine according to https://fleetdm.com/releases/fleet-4.54.0

My apologies if I'm missing something obvious, and many thanks in advance!

[sharon-fdm]

Thanks for submitting this @wolveix!
@mostlikelee, I can't recall the details, but did we not have something similar?

[sharon-fdm]

1 point to answer (and check the answer + document) that the usage here is wrong. This config should be at top level.

[wolveix]

@sharon-fdm placing it at the top-level (instead of under the config key as the docs suggest) was accepted! So perhaps this is just needs a docs update?

[sharon-fdm]

@wolveix, sounds good.
We will make sure it's documented.