video1.0<iframe src="https://www.loom.com/embed/6a99505a1f084e0e982e2398b71570c8" frameborder="0" width="1728" height="1296" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12961728Loomhttps://www.loom.com12961728https://cdn.loom.com/sessions/thumbnails/6a99505a1f084e0e982e2398b71570c8-c9c371061460a2e0.gif258.006I walk through the steps I took to fix critical bugs in Revenue Dashboard. First I corrected the Docker local development configuration so the dashboard could reach the API and load properly. Then I fixed the privacy leak by isolating the cache key, adding tenant ID to avoid collisions across tenants. I also removed unreliable backend parsing and sent raw data to the frontend so March revenue totals match. Finally I implemented timezone aware monthly calculations using each property’s local start and end converted to UTC. No action was requested from viewers.