IssueTracker

The customer is experiencing an inconsistency with Google authentication processing.The event occurred during a high-load processing period where the login processes were failing to complete.

the customer states that during a successful authentication event, the number of requests for /oauth2 and /oauth2callback should match identically. but instead, after the logs are checked, it seems these numbers are different.

Breakdown:
/oauth2: 115 items
/oauth2callback: 81 items

Customer suspects an error occurred somewhere in the process but cannot find anything in the logs.

- After checking the request log for /oauthcallback, they can see "referrer": "https://accounts.google.com/".

- The expected behavior from the customer is the following:
“/oauth2 → "https://accounts.google.com/" → /oauth2callback”.

Additional Information:
- Resource: /oauth2callback This confirms the request made successfully to the expected
  endpoint after Google authentication.
- HTTP Status: 302 (Found). This indicates a redirect.
- Referrer: "https://accounts.google.com/" This aligns with the expected OAuth2 flow.
Overall Success: There are no obvious error messages within the log.