Admin Recent Activity

Recent sessions and runs across EVERY customer workspace, in one call.

THE READ THE ADMIN CONSOLE ACTUALLY MAKES. /v2/api/activity wants "what just happened anywhere", and every list route below it is scoped to one team — so it fanned out /sessions + /runs per team and awaited all of them at once. At 40 workspaces that is 80 concurrent requests against four api lanes sharing ~40 database slots: a single team read costs 0.44s, but the fan-out measured p95 5.76s and 24.9s end to end (2026-08-27), which is why the page sat on its skeletons and why everything else queued behind it.

Authorisation is list_customer_teams' own — the local-operator gate — and the team list it returns is the exact scope of the read, so this can never reach a workspace the caller could not already list.