The ticket says login doesn't work. Your logs say nothing. User Debugging finds the user, replays every flow they ran and shows the device context that explains why, across devices, methods and retries.
Search by user ID, flow ID or external ID
Passkey readiness and lifecycle per device
Every subflow step with its routing decision
The reconstruction problem
Support escalates, engineering greps logs, nobody sees the client side. User Debugging replays it. When the same failure keeps coming back, Passkey Errors shows the pattern behind it.
It happened between app, browser and authenticator, where your logs stop. The journey record has it.
No platform authenticator, autofill off, in-app browser: readiness badges turn a mystery into a mechanism.
A passkey on the phone, a login on the laptop, a switch in between: the environment timeline keeps the story.
Three lanes: the flows a user ran, what their device could do and what happened.
Observed passkeys and their lifecycle, an environment timeline across devices and the selected flow's passkey readiness.
Common questions about per-user login debugging
Stop reconstructing failures from disconnected IdP, SIEM and APM logs. Replay the journey instead.