A script task's systems and run record

A script task runs a program you name, on a schedule or by hand, with no AI tool involved. This page says which systems a saved script task runs on, what the app shows when it does not run, and what HarmFlow keeps of each run.

The systems a script task runs on

A script task can declare the operating systems it runs on: macOS, Linux, or Windows. In the task editor, they are the task's Runs on choices.

• None declared. The task runs on every system.
• Some declared. The task runs only on the systems it declares.

A task can declare systems other than the one you are on, for example a task written on, or imported from, another computer. HarmFlow still saves it, and keeps it from running here.

On a system the task does not declare

On a system it does not declare, a script task does not run: its program is never started, whether its schedule fires or you press Run now.

• The Tasks screen shows the task with a warning that names the systems it declares and the system you are on.
• Run now starts no execution and explains the refusal, with that same text.
• A firing of its schedule is skipped, not run.
• The task editor shows the same warning, with the field it belongs to: the systems the task runs on.

What the record of a run keeps

The record of each run of a script task keeps the program as it ran:

• The program. Its arguments, or its interpreter and its whole inline script.
• The working directory it started in.
• The variables the task set.
• Its exit status.

The record keeps what ran at the time. Editing the task afterwards never changes what an older run shows.

What the record hides

The record hides secrets the way the run's output does. A token inside an argument, the interpreter's arguments, the script, or a variable's value shows as [REDACTED]. The rest of the text, and each variable's name, stay as written.