Skip to content

Check whether a build keeps failing

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-10-31.

Is this build stuck failing?

Ask whether a build target has failed several times in a row. Then read the receipts yourself.

What you get: a yes or no on whether a target is in a failure streak, measured against the alert threshold, before you spend an hour on a build that was never going to pass.

Ask in plain words:

quox · talking to Quox

Is the collector build target stuck in a repeated-failure streak? How many builds in a row have failed?

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ BOB │ bob_detect_repeated_failures target=collector ✔ BOB │ bob_detect_repeated_failures target=collector │ 0 streak, 3 threshold, exceeds threshold: false · 3.0s

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

⛓ AEE │ envelope opened · stream_success

No, the collector target is not in a failure streak. The current streak is 0 failed
builds in a row, against an alert threshold of 3.

The last 100 collector receipts all came back "ok", with no failures or inconclusive
results among them. An "ok" receipt on its own is unverified. I haven't run a live check
that the collector container is up. I can do that if you want.

16.3s · 1 tool · 0 approvals

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

Quox read the build receipts for the target and counted the failures in a row. It also said what the receipts cannot prove: an “ok” receipt means the build finished, not that the running service is up.

build history
quox build history --json[{  "id": 250,  "target": "auth",  "result": "ok",  "duration_seconds": 249,
From a real run on our own install. Host, org and stream fields left out, and only the first receipt shown.

result is how that build ended. Read down the list for the target you care about: several failures in a row is the streak.

For the newest receipt of every target at once, the build status board:

Terminal window
quox build latest

Quox read the durable build receipts and changed nothing. Queuing a new build is a separate step, quox build dispatch <target>, and a receipt alone does not prove the deployed service is healthy.