Skip to content

Check a batch of notes went in

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.2 on 2026-11-15.

Did all my notes go in?

When you load notes in one go, the load runs as one job. Ask how it went and get the count, the failures and the notes it made.

What you get: whether a batch or import finished, how many notes it created, and whether any were skipped or failed.

quox · talking to Quox

Earlier I loaded my workshop notes (the winter checklist, tool inventory and Christmas opening hours) in one go. Did that whole batch go in cleanly? How many notes came in and did any fail?

▤ AOCL │ L1 identity complete · allowed · 0ms

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

◐ QUOX │ command lookup ✔ QUOX │ command lookup │ matched: true, 1 tui, 3 cli · 1.2s

◐ NOTESQ │ search ✔ NOTESQ │ search │ 6 total, 6 count, 6 notes · 3.5s

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

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

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 4672 duration ms · 7.1s

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

⛓ AEE │ envelope opened · stream_success

The batch went in cleanly. The job (batch-8dff664f) finished with status "done". It had
3 notes in total, and all 3 were created. None were skipped and none failed, and the
error list is empty.

All three are in your Workshop collection:

• Winter service checklist
• Workshop tool inventory
• Workshop opening hours over Christmas

I also read the notes themselves, and each one carries the batch tag. The "3 errors"
label in the tool output is only a count phrase, and the error list behind it is empty.

21.1s · 3 tools · 0 approvals

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

Quox looked up the right command, searched your notes, then ran quox notes import-status. The batch finished with status done. It had 3 notes and all 3 were created, with none skipped, none failed and an empty error list. Quox named the three notes in the Workshop collection: the winter service checklist, the tool inventory and the Christmas opening hours. Quox only read.

notes ls
quox notes ls --tag batch-8dff664f --scope allTitle                                    Scope    Collection    Tags              Updated                     IDWinter service checklist                 org      Workshop      batch-8dff664f    2026-11-12T16:13:25.958Z    c99934f9…Workshop opening hours over Christmas    org      Workshop      batch-8dff664f    2026-11-12T16:13:25.868Z    8f00901c…Workshop tool inventory                  org      Workshop      batch-8dff664f    2026-11-12T16:13:25.688Z    43b52a35…🌌 QORTEX │ notes ls │ 3 of 3
From the same scratch workspace (fictional Kestrel Cycles data), run after the turn above. IDs shortened.

Every note a batch makes carries the batch’s tag, so any one of the notes tells you the tag. You do not need to have kept the job id.

notes import-status
quox notes import-status batch-8dff664fstatus: done3 created, 0 skipped, 0 failed of 3
Same workspace.

import-status takes the batch tag, the full job id, or the first 8 or more characters of the id. It works for a quox notes batch and for a quox notes import alike. It exits non-zero if the job or any note in it failed, so a script can rely on it.

Quox and the terminal read the same job. Checking a job changes nothing. If a batch went in wrong, quox notes batch-undo <job id> shows what it would remove and takes it all out with --yes, as Move notes in and out in bulk shows.