Neon Managed Auth / delivery trace

Find where the
verification flow stops.

An accepted request is only one step. Map the provider, webhook, signup gate and inbox evidence into a focused diagnosis.

Local checksNo secrets or raw logsJSON export

Your declared configuration

Which step has evidence?

1. Method & delivery owner

Verification methodEmail provider

Matching send.otp / send.magic_link event subscribed?Does the custom webhook handler send the email?Redacted webhook endpointUse a redacted hostname. No request is made to this URL.Does the webhook endpoint redirect?

2. Signup gate response

Is user.before_create enabled?Did you observe its response for this attempt?Observed HTTP statusType and value of the JSON allowed property

3. Server session setup

FrameworkIs a cookie secret configured on the server?Cookie secret length onlyNever enter the secret itself.

4. Observed result

Did the test email arrive?Did verification produce the expected session?

No input is uploaded or stored.

Repeat the browser step

Separate old cookies from a broken flow.

Use a fresh WebTraceCheck browser session to reproduce your public application sign-up and callback behavior.

Open WebTraceCheck ↗

Observe the inbox step

Give one test its own inbox.

Use CleanTempMail for non-sensitive test identities on your own app. Check arrival and complete verification before recording session success.

Open CleanTempMail ↗

Both optional products share this site’s operator. Browser access has separate sign-in and usage limits. Use permanent email for important accounts.

Read the evidence, then change the configuration.

The guide explains why webhook success, email arrival and session creation are different observations.

Read the delivery diagnosis guide →