Skip to content
Free Store
Get started
quoxcli

Read a workflow before you trust it

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.4.0, checked 2026-11-05.

What does this workflow actually do?

Get a step by step walk through of a workflow in plain words, including what happens when a step fails.

What you get: an explanation of a workflow you did not write, step by step, before you rely on it or change it. You need: a signed-in profile. About 3 minutes.

Ask Quox

Section titled “Ask Quox”

Name the workflow and ask for its steps in order:

quox · talking to Quox

Walk me through the steps of the daily-disk-usage-check workflow, in order.

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 3ms

◐ LIST │ workflows ✔ LIST │ workflows │ 1 count, 1 matched, 123 total · 1.7s

⛓ AEE │ envelope opened · ops.tool · list_workflows ok

◐ GET │ workflow ✔ GET │ workflow │ ok · 2.2s

⛓ AEE │ envelope opened · ops.tool · get_workflow ok

⛓ AEE │ envelope opened · stream_success

The  daily-disk-usage-check  workflow is active and has six steps. They run in a
straight line, one after the other.

1. Daily 08:00 UTC (schedule trigger). It fires on the cron  0 8 * * *  in UTC.
2. Prometheus, Disk Usage (metrics query). It asks Prometheus for the percentage used on
   every filesystem, sorted fullest first. It leaves out tmpfs, overlay, fuse,
   squashfs, devtmpfs, ramfs and iso9660.
3. Parse & Flag >80% (data transform). It turns the results into a list of host,
   mountpoint and usage. It flags anything above 80% and marks each line 🔴 (80% or
   more), 🟡 (60% or more) or 🟢. It also builds the report title, for example "Daily
   Disk Report, N host(s) flagged". If the query fails or returns nothing, it records
   the failure and the reason instead.
4. NOVA, Recommendations (assistant call, no tools). NOVA gets the snapshot and the
   flagged count. For each flagged host it gives a short recommendation, such as
   cleaning logs, archiving data or expanding the volume. If nothing is flagged, it
   confirms all is nominal. If the data step failed, it replies with one line saying so
   and gives no recommendations. It has a 60 second timeout.
5. Deliver to Inbox (notification). It posts NOVA's output to the inbox for everyone, at
   normal priority. The message ends with a footer showing the generation time and the
   80% threshold.
6. Fail run if data step failed (data transform). This is a final check. If step 3
   recorded a failure, the run is marked failed with the reason. Otherwise it returns
   the host count and the flagged count.

When data collection fails, step 5 still delivers a "disk check FAILED" notice. Step 6
then fails the run, so the failure shows up in the execution history as well as in the
inbox.

25.9s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.4.0, 5 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 5 Nov 2026 · test report mw2u6k

Quox found the workflow by name, read its stored definition, and explained each step: the trigger, what each node does, and how the last step marks the run failed when the data step fails. That last part is the one worth knowing before you trust a report that says “all clear”.

Do it yourself

Section titled “Do it yourself”

1. Find it and read it

Section titled “1. Find it and read it”
find and read 
quox workflow listquox workflow get <workflowId>
Commands as quox workflow --help documents them at 0.4.0.

quox workflow get shows the workflow’s trigger, its steps and its current state.

2. Validate it

Section titled “2. Validate it”
validate 
quox workflow validate <workflowId>

Validation checks the stored definition, not whether the workflow’s runs succeed. If you edited a local file, run quox workflow apply -f <file> first, because validate reads the stored copy.

3. See how its runs went

Section titled “3. See how its runs went”
runs 
quox run list --workflow <workflowId> --limit 10quox run get <runId>
See quox run list --help at 0.4.0.

quox run list --workflow shows that workflow’s runs, --status filters them by status, and quox run get opens a single run.

What just happened

Section titled “What just happened”

Quox read the workflow through its governed workflow tool, the same definition quox workflow get returns, and explained it in plain words. Reading a workflow is read-only: nothing ran and nothing changed.

Check it yourself

Section titled “Check it yourself”

Run quox workflow get <workflowId> and compare its steps with the walk through Quox gave you.

Undo

Section titled “Undo”

Nothing here changes anything, so there is nothing to undo.

Next

Section titled “Next”