{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/3664785a2efa449797c16ad168e1efda\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/3664785a2efa449797c16ad168e1efda-6f14105686fea952.gif","duration":257.491,"title":"Fixing Cache and Routing Bugs","description":"This Loom explains fixes for two main issues, focusing first on a cache problem causing incorrect revenue numbers across tenants. The author reproduces the issue by logging in to one tenant, refreshing data, then logging in to another tenant to see the same revenue, and notes they verified properties could share the same identifying value across tenants and checked existing cache behavior. They say the routing issue is also addressed by loading only tenant properties and preventing accidental subcommittee tenant data, using backend and centralized decimal handling to correct inconsistent frontend and backend results. The author ran checks, including agent-based data testing, to confirm the corrected routing and number formatting behavior."}