Skip to content
Free Store
Get started
quoxcli

Find out what starts your workflows

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 starts my workflows?

See which workflows run on a clock and which wait for a webhook, before anything surprises you overnight.

What you get: a plain list of what will run on its own and when, plus the webhook path that starts a given workflow. You need: a signed-in profile. About 3 minutes.

Ask Quox

Section titled “Ask Quox”

Start with the clock. Ask which workflows run on a schedule:

quox · talking to Quox

Which workflows run on a schedule? Give me each workflow's ID.

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ LIST │ schedules ✔ LIST │ schedules │ 9 count, 9 schedules · 4.9s

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

⛓ AEE │ envelope opened · stream_success

Nine workflows are registered on a live schedule. All nine are active and use UTC.

Workflow ID             │ Cron                │ Plain meaning        │ Next run (UTC)
────────────────────────┼─────────────────────┼──────────────────────┼───────────────
daily-disk-usage-check  │ 0 8 * * *           │ Daily at 08:00       │ 05 Nov 08:00
wf-1792166583617-2f4rtz │ 0 */6 * * *         │ Every 6 hours        │ 05 Nov 06:00
atlas-fleet-eol         │ 12,27,42,57 * * * * │ Every 15 min, at :12 │ 05 Nov 01:12
nova-devops-snapshot    │ 8,23,38,53 * * * *  │ Every 15 min, at :08 │ 05 Nov 01:08
beacon-uptime           │ 3,18,33,48 * * * *  │ Every 15 min, at :03 │ 05 Nov 01:03
forge-heartbeat         │ 11,26,41,56 * * * * │ Every 15 min, at :11 │ 05 Nov 01:11
cipher-egress-snapshot  │ 5,20,35,50 * * * *  │ Every 15 min, at :05 │ 05 Nov 01:05
sentinel-heartbeat      │ */15 * * * *        │ Every 15 min, at :00 │ 05 Nov 01:00
wf-1775391513450-f91ptl │ 0 8 * * *           │ Daily at 08:00       │ 05 Nov 08:00

Six of the nine are 15-minute agent checks. The other three are the two daily 08:00 jobs
and the 6-hourly one. The  wf-…  IDs are auto-generated, so I can't tell what they do
from the list. I can look them up if you'd like.

25.9s · 1 tool · 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 mw2u5y

Quox read the live scheduler, not the saved workflow files, so the list is what is actually registered to fire. Each row has the cron line, what it means in plain words, and the next run time in UTC.

A workflow can also be started from outside, by a webhook. Ask which path starts one:

quox · talking to Quox

Which webhook path starts the workflow wf-obj-01M4W4…?

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ QUOX │ cli ✔ QUOX │ cli │ matched: false, 7 top keys · 6.0s

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

◐ QUOX │ cli ✔ QUOX │ cli │ oversized: true, 23 full size kb, 95 total · 8.0s

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

⛓ AEE │ envelope opened · stream_success

The workflow  wf-obj-01M4W4…  is started by the webhook path  objective/01M4W4… . It
takes POST requests and enters through the node named  trigger .

It has never fired: the fire count is 0 and there is no last-fired time.

25.1s · 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 mw2u6g

The answer gives the path, the HTTP method it accepts and whether it has ever fired.

Do it yourself

Section titled “Do it yourself”

1. List the schedules

Section titled “1. List the schedules”
schedules 
quox trigger schedules
Commands as quox trigger --help documents them at 0.4.0.

This lists the active cron schedule triggers the workflow engine owns.

2. Check one workflow’s next run

Section titled “2. Check one workflow’s next run”
next run 
quox workflow schedule daily-disk-usage-check

quox workflow schedule takes a workflow id or its exact name. It says whether that workflow’s schedule is registered with the live scheduler, and when it next fires.

3. List the webhooks and events

Section titled “3. List the webhooks and events”
webhook and event triggers 
quox trigger webhooksquox trigger events

quox trigger webhooks lists the inbound webhook paths that active workflows listen on. quox trigger events lists the event subscriptions that start a workflow when something happens inside Quox.

4. Pause a schedule

Section titled “4. Pause a schedule”
pause and resume 
quox trigger pause <workflowId>quox trigger resume <workflowId>
See quox trigger pause --help at 0.4.0.

Pausing stops a workflow’s schedule firing and stays paused across restarts, without changing the workflow itself. If the workflow has more than one schedule, add the schedule’s node id after the workflow id.

What just happened

Section titled “What just happened”

Quox answered from the live trigger registry, the same one quox trigger schedules and quox trigger webhooks read. Asking and listing are both read-only: neither changes a schedule or fires a webhook.

Check it yourself

Section titled “Check it yourself”

Run quox trigger schedules and compare it with the table Quox gave you: the same workflow ids and cron lines.

Undo

Section titled “Undo”

Nothing here changes anything, so there is nothing to undo. If you paused a schedule in step 4, quox trigger resume <workflowId> turns it back on.

Next

Section titled “Next”