Steadier Sessions on Long Visits
If you spent a while moving around Componentry — hopping between bikes, activities and service logs — a page could occasionally arrive half empty. No rides, no bikes, an empty workspace. Reloading usually fixed it, which made it easy to write off as a glitch.
It wasn't random. Staying signed in relies on your session being quietly renewed as you browse, and the renewed session wasn't making it back to your browser. So your browser kept presenting credentials the server had already retired, and every page asked for a fresh sign-in all over again. Do that often enough in a short space of time and the sign-in service starts turning requests away — which is the moment a page comes up blank.
Your session is now renewed once and handed straight back, and each page asks for it a single time instead of repeatedly. Long sessions stay steady, and pages stop arriving with pieces missing.
This one compounded with company: because the requests came from our servers rather than from individual browsers, one very active session could use up headroom that other riders were relying on at the same time. Fixing it takes that pressure off everyone, not just the rider who happened to trigger it.