{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6a99505a1f084e0e982e2398b71570c8\" frameborder=\"0\" width=\"1728\" height=\"1296\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1296,"width":1728,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1296,"thumbnail_width":1728,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6a99505a1f084e0e982e2398b71570c8-c9c371061460a2e0.gif","duration":258.006,"title":"Fixing Revenue Dashboard Critical Bugs Successfully 🚀","description":"I 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."}