Stage 7 · Runs and operations

Once a workflow works, you need to understand what it did, and manage it over time. This stage covers how.

Inside a run folder
run.json, blocks/ logs, files/, retention, and what is masked.
Pause, resume, edit the rest, stop
Control a run in flight and change the blocks that have not started yet.
Notices and Workflow settings
Run notice cards and the Settings → Workflows defaults.
termorq-cli workflow
List, run, and inspect workflows from a terminal or a script.
Troubleshooting playbook
Symptom → cause → fix for the errors you will actually hit.

Inside a run folder

Goal

Find and read everything a run left behind. Time: 10 minutes.

workflows/runs/<workflow id>/<run id>/
├── run.json      # the run record: blocks, inputs passed via uses, outputs, status
├── blocks/       # per-block logs (secrets masked)
└── files/        # cwd for code blocks; artifacts written via TERMORQ_OUTPUT

Settings → Workflows shows where this folder is on your computer.

From the Runs tab

Open a workflow and choose Runs (or choose Runs on its row in the list).
Select a run. Every block captured when the run started is listed, with its values from uses, resolved requests, outputs, and text or error.
Copy input and Copy output copy those values for a block. Secrets stay masked.
Loop body blocks appear once per pass.
Open folder opens the run directory, and Delete run removes it, including files/. Delete asks first, and focus starts on Cancel.

Drag the divider to give the history list or the run details more room.

Retention

Termorq keeps the newest 50 runs per workflow (configurable in Settings → Workflows). Each new run deletes the oldest folder beyond the limit. The disk use shown in the workflow list counts the definition plus all of its run files.

Warning

files/ is deleted along with the run. Copy any artifact you want to keep somewhere else, for example by adding a final Code block that copies it to $TERMORQ_FOLDER/reports/.

Check your run

Run Output rules from Stage 2 that writes report.csv, then click Open folder: the file is in files/, and run.json lists the emit block’s outputs.

Exercise

Add a final block that copies report.csv into $TERMORQ_FOLDER/reports/<run id>.csv.

Details

set -euo pipefail
mkdir -p "$TERMORQ_FOLDER/reports"
cp "$TERMORQ_OUTPUT/report.csv" "$TERMORQ_FOLDER/reports/$TERMORQ_RUN.csv"
jq -nc --arg p "reports/$TERMORQ_RUN.csv" '{ok:true, saved:$p}'

Pause, resume, edit the rest, stop

Goal

Stop a run going wrong, or fix the remaining blocks mid-run. Time: 10 minutes.

Action	Effect
Pause run	Lets the active block finish, then holds the next one
Resume	Continues from the held block
Edit rest → Apply	Changes the blocks that haven’t started in this run only. It doesn’t write the workflow file
Edit workflow → Save	Changes the file, which affects the next run
Stop	Cancels the active process tree or request immediately, without asking
Cancel run	Available during credential preflight, before any block starts

Rules

A workflow has one active run at a time. A second start is recorded as Skipped · already running. Different workflows can run at the same time.
If Termorq quits while a run is in progress, that run is shown as stopped and its partial folder stays.
termorq-cli workflow run blocks the CLI process. Quitting the app stops it.

Check your run

Add sleep 20 to the first block of a three-block workflow. Run it, Pause it, use Edit rest to change block 3’s output, Apply, then Resume. Block 3 uses the edited version, and the saved file is unchanged.

Exercise

Start the same workflow twice quickly, once with Run and once with its HTTP trigger. What does Runs show?

Details

The second start is recorded as Skipped · already running.

Notices and Workflow settings

Goal

Tune how runs report their progress, and the defaults for new workflows. Time: 5 minutes.

Notice cards

One card per run, shown above the footer, with at most two in-progress cards. These are not OS notifications.
The card appears when the run starts, updates as each block starts, and changes when the run fails or finishes.
A success card disappears after 6 seconds. A failure card stays until you dismiss it. Open goes to that run.
Progress isn’t shown while that run’s page is open.
Control which cards appear for each workflow with the root notices: key (see Stage 6).

Settings → Workflows

Setting	Default
Listener host	`127.0.0.1`
Listener port	`8787`
Network bind	Off (this machine only)
Notice cards	On
Block timeout	600 seconds
Runs to keep	50
Code editor › Insert highlight clears after	10 seconds
Code editor › Undo notice stays open for	10 seconds

Search Settings for workflow, listener, or undo notice to find these.

Check your run

Set Runs to keep to 5, run a workflow six times, and check that Runs lists only 5.

Exercise

Which setting would you change so that Autogenerate’s teal highlight stays for 30 seconds?

Details

Settings → Workflows → Code editor → Insert highlight clears after: 30 (the range is 1–60).

termorq-cli workflow

Goal

Run a workflow without opening its page. Time: 5 minutes.

Pro feature

termorq-cli workflow is Pro. A Free binary leaves it out of --help and refuses the command.

termorq-cli workflow list
termorq-cli workflow list --workspace ~/src/acme-apis
termorq-cli workflow run refresh-acme-users
termorq-cli workflow runs refresh-acme-users

Command	Prints
`workflow list`	Each workflow’s name, ID, and source (`included`, `yours`, or `workspace`)
`workflow run <id>`	Starts the run and waits in this process
`workflow runs <id>`	The run directories under `workflows/runs/<id>/`

--workspace takes an absolute path or one starting with ~.
A file with a problem prints the same sentence as Save, and the run doesn’t start.
Schedules and the HTTP listener belong to the desktop app. The CLI starts only the run you name.

Check your run

termorq-cli workflow run hello-workflow finishes, and workflow runs hello-workflow lists the new directory.

Exercise

Write a one-line shell command that runs hello-workflow and then prints its newest run directory.

Details

termorq-cli workflow run hello-workflow && termorq-cli workflow runs hello-workflow | tail -1

Reference: termorq-cli workflow

Troubleshooting playbook

Goal

Diagnose a failed run in under a minute. Time: reference.

Symptom	Likely cause	Fix
`TERMORQ_INPUT` is unset in a full run	`uses` is empty	Add the paths the block needs to `uses`. `input_sample` doesn’t supply them
`'trigger.text' is not available`	A manual run, or a trigger that doesn’t send `text`	Use an HTTP or Telegram trigger, or read `inputs.<name>` instead
`… is not a property this block can use.` (on Save)	Undeclared output, input, or secret, or `loop.*` used outside a loop	Declare it, or fix the path
`The last non-empty line of code output must be a JSON object`	Pretty-printed JSON, a trailing log line, or an array	Print one compact object last, and send logs to stderr
A declared property is missing or has the wrong type	`"2"` vs `2`, `"true"` vs `true`	Match `outputs.properties` exactly
A JSON parser rejects Step input	Plain text, or the wrong nesting	Type `{"trigger":{"text":"…"}}`, or read the input as text
`Name a saved endpoint, or use mock://.`	A direct `url` to a real host	Save the endpoint, and set `endpoint:`
`HTTP 4xx/5xx.`	The API rejected the request	Check the resolved request on Runs
`MCP arguments must resolve to a JSON object.`	Template text that isn’t an object	Serialise the arguments in a Code block
An AI block fails with declared outputs	The model didn’t end with a JSON object	Tighten `system`, and raise `max_tokens`
A Code file can’t import a sibling file	The source is copied to a build directory	Make it self-contained, or use `$TERMORQ_FOLDER` paths
A runtime can’t start	It isn’t installed, or isn’t on `PATH` for the app	Install it, then restart Termorq
`'kind' must be code, code_file, …`	`kind: git`	Use Code file after checkout
An MCP block fails before calling the tool	Credential lookup or connection failed	Open `@logs`
Skipped · already running	A run was already active	Wait, or Stop the active run

Check your run

You can match each Stage 2–5 failure you caused deliberately to a row in this table.

Exercise

A block prints {"count": 3} followed by done., and its output schema declares count. Which row applies, and what is the smallest fix in Bash?

Details

The last-line row. Change echo done. to echo done. >&2. The added >&2 sends it to stderr.

Stage 7 · Runs and operations

Subsections of 7 · Runs & ops

Inside a run folder

From the Runs tab

Retention

Pause, resume, edit the rest, stop

Rules

Notices and Workflow settings

Notice cards

Settings → Workflows

termorq-cli workflow

Troubleshooting playbook