We're currently attempting to fetch user data on every page load (even if the authentication session is not set). This creates unnecessary pressure on the API deployments after sending a mass email. Since we're using database-based persistent sessions, Django will open a db connection even on a request that's missing authentication creds, to return session id along with the 403 response.
Instead, we should only attempt to fetch user data if an auth session is set in browser local storage.
Describe the bug
We're currently attempting to fetch user data on every page load (even if the authentication session is not set). This creates unnecessary pressure on the API deployments after sending a mass email. Since we're using database-based persistent sessions, Django will open a db connection even on a request that's missing authentication creds, to return session id along with the 403 response.
Instead, we should only attempt to fetch user data if an auth session is set in browser local storage.