process management

---

adding a process

1. Click on a machine in the dashboard.
2. Click add process.
3. Fill in the current dialog fields:
   • name: display name, such as TouchDesigner.
   • launch mode: off, always, or scheduled. off leaves the process unmanaged, always keeps it running, and scheduled runs it only during configured schedule blocks.
   • executable path: required path to the executable, such as C:\Program Files\App\app.exe.
   • file path / command arguments: optional file to open or command-line arguments to pass to the executable.
   • working directory: optional directory to run the process from.
   • task priority: low, normal, high, or realtime.
   • window visibility: normal or hidden; hidden is intended for console apps only.
   • launch delay (sec): seconds to wait before launching.
   • init timeout (sec): seconds to wait before responsiveness checks begin.
   • relaunch attempts: crash-restart attempts before the process is treated as failed.
   • schedule configuration: always open in scheduled mode, and available in off or always from the configure schedule button at the end of the launch-mode control. Edit one or more blocks with days and start/stop ranges. The editor names the clock those times are read against — each machine's own by default, or the site's timezone if the site has opted into site time (timezones). Blocks saved from off or always are stored with the process and do not change its launch mode.
4. Click create process.

The agent receives the new configuration and begins monitoring the process.

---

editing a process

1. Click edit on a process row or card.
2. The edit process dialog opens with the current settings.
3. Edit any fields.
4. Click save changes.

Changes propagate through Firestore to the agent immediately.

---

process actions

From the process row, machine card, or edit dialog, the dashboard exposes these actions:

Site admins on the site and superadmins have MACHINE_CONFIG_WRITE and MACHINE_EXEC_COMMAND. Members can view process state and configuration, but they are read-only for create, edit, delete, schedule, launch-mode, restart, and kill actions.

Restart and kill actions send commands to the agent. Create, edit, delete, launch-mode, and schedule changes update the machine configuration that the agent watches.

When a process is changed from off to scheduled, the agent clears stale killed/cooldown markers immediately. If the current time is outside the schedule window, the process stays stopped until the next matching window, then launches normally.

If the configured executable path no longer exists, the agent aborts the launch and the process shows as STOPPED (INACTIVE means launch mode is off, not a missing file), and the dashboard shows an error toast. When the agent finds likely sibling executable paths, the toast lists up to two suggestions and the use path action opens the edit dialog with that path pre-filled.

---

schedules

A process in scheduled launch mode runs inside blocks: a set of days plus one or more start/stop ranges. A range whose stop time is earlier than its start is an overnight window and carries into the next day.

The editor previews the whole week as a seven-day bar — one column per day, with a coloured segment for every range. Each block keeps its own colour, so a process with a morning block and an evening block reads at a glance, and a pattern that accidentally covers only four days is obvious before you save. The same bar appears on the process row and on the schedule preset list.

Rather than rebuild a common pattern on every machine, save it once as a schedule preset and apply it. Four presets are built in, including business hours and 24/7.

Windows are wall-clock rules, not absolute instants. Which clock they are read against depends on the site — see timezones.

---

process settings reference

---

tips