Corbado Observe · User Debugging

From support ticket to exact journey

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 the email, phone number or username a user gives support
• Passkey readiness and lifecycle per device
• Every subflow step with its routing decision

The reconstruction problem

Why login tickets take hours to answer

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.

Logs don't have the answer

It happened between app, browser and authenticator, where your logs stop. The journey record has it.

Capabilities explain failures

No platform authenticator, autofill off, in-app browser: readiness badges turn a mystery into a mechanism.

Users switch devices

A passkey on the phone, a login on the laptop, a switch in between: the environment timeline keeps the story.

User Debugging

One user, the whole story

Three lanes: the flows a user ran, what their device could do and what happened.

1. The device context that explains the failure shown
2. Every step of the journey as a card open
3. Watch a ticket get debugged open

User Debugging FAQ

Common questions about per-user login debugging

How do I find a user?

What is in the device context?

What does a subflow card tell me?

How deep can I go?

What about user privacy?

Answer the next login ticket in minutes

Stop reconstructing failures from disconnected IdP, SIEM and APM logs. Replay the journey instead.

• The exact journey, not a log-based guess
• Device capabilities that explain the why
• Read-only on top of your existing IdP