weft-debugging

# Debugging a run ## Reading a run Each verb below prints one compact line per run or per event and has a flag that opens the part you want, so a forty-node run reads without loading the whole journal. You read in this order and stop when you hold the failing node and the wrong value. - **If you want to know what ran, or whether your trigger fired since the change**: `weft runs --limit 10 --phase fire` (`--node <trigger>` for one trigger's runs, `--since 10m` for the recent ones, `--status failed` for the ones that broke). One line per run: run id, status (`running`, `waiting_for_input`, `completed`, `failed`, `cancelled`), phase, the start time in UTC, the project id, the entry node (the trigger that fired), the tags. An activate, a resync or an infra start creates setup runs, phases `trigger_setup` and `infra_setup`; `--phase fire` hides them. `--project <id>` narrows to one project. A run whose trigger has `recorded: false` is listed only if it failed (with the node that failed and why, nothing before it) or reported a cost or asked weft for something on its behalf, so a route that answered and left nothing here may simply be unrecorded: `weft status` shows how many runs each trigger started in the last minute or two and how many failed, which is how you confirm its runs happen. - **If a run failed and you want the reason**: `weft logs <run-id>`. It prints what the run's nodes wrote and every failure the journal recorded, as `error` and `warn` lines. A line about one node names it (and the loop iteration, `llm#3:`); a line about the run itself (the run failing, a cancel) names none: `[2026-09-02 21:36:47] error llm: node failed: the service answered 401 ...`. It is the last 1000 lines and says so when the run wrote more; `--limit` raises that up to 20000, higher is refused. For most failures this is enough and you never open the events. `(no logs: ...)` means the run wrote nothing and recorded no failure: it did not fail, so you check its status. - **If you want the values on the wires**: `weft events <run-id>`. One line per event: UTC time, kind, node, then everything the row carries as `key=value`, each cut to a screen's width (`input=` on `node_started`, `output=` on `node_completed`, `error=` on `node_failed`, `reason=` on a skip or a cancel, `token=` on a suspension, and so on). You narrow before you read: `--kind failed` for the failures (a substring matches, so this catches `node_failed` and `run_failed`), `--kind node_skipped` for what did not run and why, `--node <id>` for every event on one node, `--iteration 3` for the fourth time round a loop (counted from 0; `3.0` is the first iteration of a loop inside it, outermost first). - **If a value on one of those lines is cut off**: it was cut to fit the screen, not stored short. `weft events <run-id> --node <id> --full` prints it whole, and `--json` gives you the replay rows for `grep` or `jq` (their field names are camelCase, like `runId` and `atUnix`, and a kind is a snake_case value, like `node_skipped`). No value a run recorded is unreadable, so you never report one as unreadable. - **If a client says it missed part of a stream or a socket's messages**: `weft events <run-id> --kind caller` is the conversation with its caller. A `caller_window` line carrying `dropped=12,13 (the caller read too slowly and never received these messages)` means the trigger's `whenCallerIsSlow` let them go; under `block` that never happens. A `caller_disconnected` line carrying `dropped=...` names what was still waiting to go out when the exchange ended. The numbers are the messages' offsets, the same `offset` the window lines carry, so `--full` shows what each one held. A `caller_errored` line saying `a chunk was dropped and the exchange went on` is a message the program could not make, skipped because `whenChunkFails` is `drop_chunk`; the rest of the line says why. Every other message the program sent went out to the caller, so if none of these names the missing one, the program never sent it: walk back to the node that should have. - **If a node did not run**: its `node_skipped` line carries the reason. `did_not_flow`: the node's `_should_flow` said no. `flow_closed`: nothing ever answered its `_should_flow`, so walk to whatever drives that wire. `required_input_closed` names the input that arrived closed, so walk to that node's line. `every_input_closed` and `one_of_group_closed` are the same story for a node with no required inputs and for a `@require_one_of` group. `scope_skipped` names the group or loop that did not run, taking this node with it: walk to that container, whose own reason is its gate saying no, or `every_input_closed` when every wire into it closed with nothing on it. (One group input arriving closed while another brings a value is not this: it passes through to the nodes inside that read it, and they carry their own reason.) `wait_skipped`: the node was waiting on a person (a form, a question) and they skipped it, so it ends with nothing sent on and what reads it skips: not a bug to chase. - **If a `Debug` shows `output=` empty**: correct, a `Debug` has no outputs. Its value is on its `node_started` line as `input=`, or `weft events <run-id> --node <debug id>`. - **If a past run shows no values at all**: a run's rows say what happened, not what it meant; the editor works out every input and output by replaying those rows against the code the run ran, so a run whose code [the daemon] no longer holds shows every node with no values, and the run itself says why. The empty graph is not "the node produced nothing" and not a viewer bug. The code is kept as long as any run points at it, so this is rare. If the files are still on disk, `weft build` puts the program back under the hash the run names and the run reads as it did. If not, the run is readable only as its shape, and `weft clean <run-id>` removes it. - In VS Code with the weft extension: the Runs view, "View in Graph" replays the run in the graph, values on every wire; `Debug` nodes render their latest value inline. For the full editor surface (inspector, action bar, targets, everything clickable), go and read the `weft-editor` skill. ## The debugging playbook 1. **It does not compile.** Read the diagnostics: `line:column message`, a stable slug, and the message names the fix. You fix what it names; you never route around a diagnostic. `weft validate --file src/main.weft < src/main.weft` re-checks without building. A diagnostic naming the catalog (an enrichment error, an unknown field, "a stale base_catalog copy") means the stdlib copy lags the installed weft: `weft catalog update`, then re-check, before anything else. A command refused with `it needs parts of the program that do not compile:` lists each broken part with its file and line, and only those stand between you and the run: fix them, or cut the run so it does not reach them. A part reading `package '<name>' didn't compile: <first error>; its full errors are in the build log: <url>` is a node package the worker was built without: the log at that address has the whole compiler output. 2. **A run failed.** `weft logs <run-id>` names the node and the error. If that is not enough, `weft events <run-id> --node <that node>` shows the values that reached it, on its `node_started` line. For the compiler error slugs, go and read the `weft-language` skill. A node's own error text is written by the node's author. A run, an activate or a resync is refused before it starts while a connection it needs is not picked, naming the `weft connect` that picks it, and a node error saying it has no connection picked is the same [the runtime tier] gap, not a source bug: you pick a stored connection yourself (`weft connect --node <id> --grant <grant>`) or send the user to the node's Connect button / `weft connect` in their terminal, then run again. A failure saying `the worker running '<node>' went away while it was running` means the worker of a durable run died while that node was running: weft does not run a node again once its start is on record, because what it did may have partly happened. Check what it did outside (the email, the row, the post), then, if it has to happen again, start a run at that node by hand: `weft run --from <node>=<inputs>`, with the inputs from `weft events <run-id> --node <node> --full`. If the message says `went away while it was reading a stream` instead, the items it read are gone from the stream, so `--from` cannot hand them back: check what it did, then run the whole run again. 3. **A value is wrong, not failed.** Work upstream from the output: open the run, look at the top-level groups, find the first whose output is already wrong, descend, repeat. When you hold the concrete failing case, iterate on that one node (build, run, look) and feed the earlier stages' passing examples through again. 4. **Suspended.** Expected for human-in-the-loop: nothing is wrong. A suspended run is alive and costs nothing: the `HumanQuery` parks, the worker exits, and the answer resumes it. The person answers in the browser extension (built with `./setup.sh --browser --no-sign`). If nobody should have been asked, the bug is the `_should_flow` that routed into the person. A run waiting on an outside job (a render, a crawl) is suspended the same way, and `weft node-state <run-id> <node>` prints the last answer its wait read from the service (`last answer: ...`), which the editor also shows on the waiting node while you follow the run. 5. **Cancelled.** Read the reason on `run_cancelled`. `Cancelled by user` is a person or a take-down: the Stop button, `weft stop`, a take-down that cancelled the runs going (`--running cancel`) or dropped the paused ones (`--held drop`), `weft rm`, or a cancel through a signal token. A run the infra health check stopped says so (`the infra health check found 'db' broken and took down the triggers that read it, stopping their runs`), and `Stopped by run <run-id>, which took its triggers down` means a program's own run took those triggers down: look at that run. `Stopped by run <run-id> (tag <tag>)` means another run asked the engine to stop everything carrying that tag: look at **that** run, and if no sibling was supposed to stop this one, the bug is in whichever node tagged and stopped it (`weft runs` shows each run's tags, so you see which runs shared it). `Caller disconnected` means the live caller this run was answering went away: it hung up, closed its socket (or never opened it), missed its heartbeat, or sent a message the connection refused. `the worker running this run went away; a fast run lives in its worker's memory, so it is not run again` means a fast run lost its worker (a crash, a machine gone): check what it did outside, then start it again (let the trigger fire again, or fire it by hand: `weft bake`, then `weft run --fire <trigger>=<payload>`, with the `payload` on the trigger's `node_kicked` line in `weft events <run-id>`), and if the trigger's runs have to carry on after a worker dies, set `durable: true` on it. A durable run whose worker stops or dies is never cancelled: another worker picks it up from its record, and only the node that was running fails (item 2). `the run had to leave the copy of the program running it (...), and it cannot be suspended: <why>` means its worker was stopping and this run could not move to another one; the `<why>` names the reason: its trigger has `recorded: false`, its route does not have `outlivesCaller`, or a bus between its nodes was open. Check what it did outside, then start it again the same way as a fast run that lost its worker. `its worker refused it 3 times: <error>`, `the platform refused weft's calls for it 3 times: <error>` and `its project's worker settings kept it from any worker 3 times: <error>` mean a queued run (a `weft run`, a resume) never got going: it got a no, then again 5 seconds later, and again 20 seconds after that, the reason names who said the last one, and `<error>` is that no. Only an answer counts as a no. When weft calls the worker, any error the worker answers is a no, except its busy `503`. When Cloud Run answers in the worker's place, a `4xx` other than `404`, `408` or `429` is a no, and those and a `5xx` are no answer. When weft asks Google Cloud to create the worker, a `400`, `401` or `403` is a no (the `<error>` carries its words), and a `429`, a `5xx` or a timeout is no answer. Worker settings that together are a shape no platform could run are weft's own no. A worker answering busy makes the run wait and spends no try, for as long as the workers answer busy. Each wait is as long as the run has been turned away so far, at least 5 seconds and at most a minute. Once that lasts longer than the install's alert delay (`alert_after_minutes`, 5 minutes by default), `weft status` lists it under `waiting on weft:` (item 11), ending in ``this project's worker has answered busy for <time> (memory full); raise its memory (`weft workers set --memory <size>`)``, and a Google Cloud install emails an alert. A worker still starting makes the run wait for it, and a call that got no answer at all is tried again 5 seconds later and again 20 seconds after that. After a third with no answer the run is not ended: it waits, queued, until a worker of its project comes alive or a build of the project registers, and then its tries start over. Item 11 says whether the workers are still out of reach; once you have fixed them, changing the project's worker settings (`weft workers set` or `reset`) lets every run still queued try again from zero, but a run already cancelled stays cancelled, so start it again. A reason starting `run <run-id> stopped ... before the ... minute limit this platform puts on ...` is a time limit on a cloud install, and the rest of it says how to stay under that limit. Its cancel cause has the kind `limit`, `weft tree` prints it as `(a time limit: ...)`, and a caller still connected was answered `504`. A run whose caller's session reached the route's or socket's `maxSessionSecs` is a time limit too, on any install, and its reason reads `run <id> stopped when its caller's session reached the <n> second limit its trigger sets (maxSessionSecs), and the caller was told it was a time limit (a 504, or close code 1011 on a socket). A session meant to last longer raises maxSessionSecs, or sets it to 0 for no limit`. An older run cut by a time limit carries the kind `runtime` instead. Anything else is the runtime's own reason, printed as words. 6. **Stuck.** The engine proved nothing can proceed; that is a graph-shape bug (a wire the compiler could not catch). The `run_failed` line names every firing left holding a pulse and the wired ports it never received (`theirs has value, still waiting on go`): walk to whatever should have driven the missing port. 7. **Nothing ran.** Nothing reached the branch: check that the trigger that should have fired is on, then walk from it down to the first `_should_flow` or required input that closed. If the trigger is off, `weft status` says on its line whether it was taken down with its infra or by the health check, and adds `held back: <why>` when it cannot come back yet; one that only reads `off` was turned off by hand. The `weft-running` skill, "Taking triggers down, and bringing them back", says what brings each one back. If it fired and no run came of it, `weft status` says what the event waits on, under `triggers:`: - `<N> fires wait until the instance's values change: <reason>`, `... until the infra the runs read is running again: <reason>` or `... until the install picks the connections the runs need: <reason>`: nothing moves until you fix what the reason names. - `<N> fires stopped after failing to start a run, and holds the trigger's queue`: handing the event to a worker failed (the worker could not be reached, the run could not be recorded), then again 5 seconds later, and again 20 seconds after that, so it stopped, and the events behind it wait in order. `weft activate`, a new build or a change of the worker settings tries again. A fire waiting for room (a limit reached, permits taken) or for its trigger to come back on gets no line there. One waiting for room tries again by itself, waiting longer each time, up to 5 minutes; one waiting for its trigger is handed over when the trigger is activated again. 8. **Too much is running.** The one failure nobody reports, because nothing errors: runs accumulate and the only symptom is a list that keeps growing. Every live connection is its own run for as long as the caller holds it, so a page anyone can open, or a client that reconnects by itself, can leave one behind per visit. `weft runs` is the check, and what you look at is the STANDING count of runs still going, not whether the one you started finished. Drive the thing, close it, look again: the count comes back down, or you have found a leak. Several runs of one trigger that never end is a finding you report, with the count and how long they have stood. 9. **A timer or a wake that never arrived.** A wake the receiver refuses for good is dropped once, with one error in `weft daemon logs` naming it, the status and the answer (on a local install: a `400`, `413`, `415` or `422`; the listener answers a wake it cannot read `200` with `dropped` and logs it). Any other failure (another `4xx`, a `5xx`, no answer) is sent again later, waiting longer each time. So a wait that never woke is read in `weft daemon logs`. A trigger's own timer, schedule, poll or subscription renewal whose wake keeps failing has 20 tries (`wake_attempts` on a cloud install), and a try is a delivery the listener answered with anything but a 5xx: while the listener is down, or it or something in front of it answers a 5xx, none is spent. On the user's own machine the 20 take about an hour when the listener answered every one, and up to about 95 minutes when an outage had already stretched the wait between tries to its longest, 5 minutes. After the 20th failed try the trigger is given up and stops being woken, and its node shows `its wake failed each of the 20 times the listener handled it, the last with: <error>`. A wake that did its work but could not set the next one shows `its wake was handled, but the wake after it could not be set on the last of the 20 times the listener handled it, so nothing wakes it again: <error>` instead. One whose connection only a person can fix (it is gone, needs reconnecting, or lacks a permission: the broker answers 400, 404, 409 or 410) is given up at once. A trigger that keeps a connection open (a socket, a stream, an SSE subscription, a service's events) retries by itself, and its live panel shows `reconnecting since <time>: <error>` meanwhile. On a failure only a person can fix (those same answers, a credential refused right after it was fetched, a setup error that fails the same way every time) it stops instead: its live panel shows `stopped: <why>`, and the reason stays on its node. A service that is busy or limiting calls is still retried. If you want either kind back and its connection was the trouble, reconnecting that connection is enough: weft brings back every trigger that uses it. For anything else, a setup error for instance, fix it: when the fix changed the program, `weft resync` sets the trigger up again on the new version; when it did not (a public address opened, say), a resync finds nothing behind and does nothing, so `weft deactivate --trigger <node>` then `weft activate --trigger <node>` sets it up again. A plain `weft activate` does not, because the trigger still counts as on. 10. **[the daemon] unreachable** (connection refused, an editor button that does nothing). You read, never restart: `weft daemon status` and `weft daemon logs --tail 50` say what [the daemon] is doing. Then you tell the user the symptom (the exact refusal, and what you were running) and stop; bringing [the daemon] back is their install's job. If you catch yourself typing `weft daemon start`, `stop` or `restart`, stop and write: "Wait. The daemon is not mine to restart." Then report the symptom. 11. **A part of weft keeps failing.** `weft status` lists it under `waiting on weft:`, one line each, as `<what> (failing for <span>, last tried <span> ago; <what happens next>): <error>`, and the line stays until it is fixed. The lines naming one of weft's parts or jobs, the bucket line, the news line and the line about removed projects are install-wide, so every project shows them, and you restart none of those parts: report the line to the user as printed, as for [the daemon] in item 10. The other lines are this project's own. - `weft's supervisor, which starts and stops infra, cannot be reached` (or the dispatcher, or another part named the same way): weft tries it again on the next change that needs it, and the line goes once weft reaches it. - `this project's workers, which runs are handed to, cannot be reached or cannot take them`: what happens next reads `a queued run refused 3 times ends, and one its workers could not be reached for 3 times waits until a worker of the project comes up or a build of it registers; one they keep answering busy (which spends no try) is tried again after a pause that grows to a minute, for as long as they do; changing the project's worker settings (more memory, for a worker that stays busy) tries every queued run afresh` (the run that ends is cancelled, item 5). The line goes once none of the project's queued runs still waits on its workers (answered busy, refused, or not reached) and a run of the project has since left the queue: the last one that waited (it reached a worker, ended, or was cancelled), or one started after the failure. A change of the project's worker settings clears it too. - `weft's <role> could not <what the job does>` (say, `hand queued runs to workers`), followed by `weft tried a few times and stopped; it tries again on the next change that concerns it`: this line appears only on a cloud install. A pass of one of weft's background jobs failed, was tried again 1 second, 5 seconds and 20 seconds later, and failed each time, so it stopped and wrote its error here; Google Cloud's queue does not keep calling it. The job runs again on the next change that concerns it, and the line stays until a pass goes through. - `weft's supervisor could not get through this project's infra`: the error says what it could not do. When the supervisor could not list what the host holds (`could not list what the host holds to delete what its gone copies left`) or read which projects it owns (`could not read what it owns to look at its health`), its whole pass failed, and every project it holds counts a failed pass. On the user's own machine it ends `(tried again at the supervisor's next look)`, and the supervisor never gives up. On a cloud install it ends `(failure <n> in a row; tried again in <s> s)`, 5 seconds after a first failure and 10 after a second, or, at the third, ``(failed 3 times in a row, so the supervisor stopped trying; `weft infra look` tries again)``. A pass that goes through starts the count again from zero. A health rule whose action (taking down the triggers that reach a broken copy, or bringing them back) kept failing shows in this line as `its health rule '<name>' on <copy> failed <n> times: <error>`. Once you have fixed what the error names, run `weft infra look`: it starts a fresh round of tries and gives every health rule that gave up another go. The line goes once a try over the infra goes through. - `weft's supervisor could not delete what the infra host still holds of removed projects (their disks included)`: the error names each removed project, what went wrong and what happens next. On the user's own machine that is `(tried again at the supervisor's next look)`. On a cloud install it is tried again 5 seconds, then 10 seconds later, and the third failure ends `(failed 3 times in a row, so the supervisor stopped trying; its next pass tries again)`. From then on every pass of the supervisor tries again, and `weft infra look` in any project starts one. The line goes once the host holds nothing of any removed project. - `weft's supervisor gave up infra commands of this project it could