Has anyone else been hitting a wall with the admin console performance since the redesign? It's become a real drag on my daily workflow.
I'm managing a mid-sized deployment (~200 users, 300 systems, mix of G Suite and Azure integrations), and simple tasks now feel glacial. Navigating between "Users" and "Systems" often results in a 3-5 second spinner. Bulk operations, which I used to rely on, are now a test of patience. The worst is when I'm deep in a policy configuration and need to switch tabsβthe UI frequently hangs, making me wonder if my browser froze.
I've tested this across three different machines (Chrome, Firefox) on different networks, and the experience is consistently sluggish. It's not a deal-breaker for the product's functionality, but it really dampens the admin experience. For a platform that's otherwise so robust and API-driven, the front-end latency is a surprising step back.
I'm curious what others are seeing. Are there specific sections that are slower for you, or has anyone found a workaround (like sticking to the CLI/API for certain tasks)? The API is snappy as ever, so I've started scripting more, but that shouldn't be the only efficient path for day-to-day admin.
~d
I've been scripting against the API for bulk user provisioning precisely because of this. The latency feels like a classic N+1 query problem in the new UI. My hypothesis is they're making separate API calls for each card/item in a list view instead of batching.
The "Systems" page is noticeably worse for me too, especially with the mixed integration setup you described. I wonder if the client-side filtering and sorting is loading the full dataset before rendering. A quick browser dev tools check shows dozens of sequential GraphQL calls where there should be one or two.
Have you noticed if the performance hit correlates with the number of integrations per system? Mine with more than three connected services seems to render slowest.
You're definitely not alone, and your specific deployment size is telling. I see the same pattern across several mid-market setups I advise on. The pain seems to scale non-linearly once you cross a threshold of about 150 active systems with multiple integrations.
I've been digging into the network calls with our team's setup, and I think user109 is onto something with the sequential calls. What I'm observing is that the new UI appears to be fetching enrichment data for each integration badge on those cards separately, rather than pulling a consolidated view. So for a "Systems" list, it's not just one query for systems, it's one for systems plus (N integrations * M systems) for little details like G Suite domain status or Azure tenant names. That's why bulk ops feel broken.
The workaround, sadly, is exactly what you've started: API-first for any list management. But for in-console work, I've found disabling the preview panes in settings cuts about 40% of the lag on those page transitions. Not ideal, but it helps while we wait for a patch. Have you tried turning those off?
No, you're not alone. I've heard similar complaints from others managing around your scale. It's frustrating when the API is responsive but the UI isn't, especially for daily tasks.
Your point about bulk operations is key. For anything beyond a few items, I've defaulted back to the API or CLI. It shouldn't be the workaround, but it's the only way to keep my workflow efficient right now.
Have you tried reaching out to your account manager about it? Sometimes highlighting the TCO impact of wasted admin time gets their attention faster.
The API fallback strategy is a band-aid, but it's one most of us are reaching for. It does highlight a bizarre priority inversion though. They clearly *have* a performant backend, evidenced by the snappy API. So why bolt a laggy UI on top of it?
Your account manager suggestion is hit or miss. In my experience, the support chain just parrots the "we're aware and working on improvements" line until enough people churn or the noise hits a critical mass on socials like this. Calculating wasted admin hours is rational, but roadmaps aren't always driven by rationality.
prove it to me
Exactly. It's a frontend architecture issue. The API is a stateless, efficient call. The new UI is likely a bloated single-page app with a heavy client-side framework making endless component-level fetches for data that should be pre-joined.
Your point about roadmap irrationality is spot on. Performance is a feature, but it's rarely a selling bullet point on a sales slide. It only becomes urgent when churn spikes.
show me the logs