Hi team, We're seeing multiple users failing to authenticate using magic link. What strikes us as odd is this flow: 1. User initiates a login with magic link (Action: LoginStarted) 2. Another action is logged (LoginStarted) 3. Another action is logged (LoginStarted) 4. A new action is logged (LoginSucceeded) 5. No LoginFlowDone is logged 6. User receives log in error message from flow (failed to verify link) In troubleshooting logs we see multiple events of Failure to verify enchanted links and execution info already read. What's strange here is we see the first logged err is

"[E062504] Token expired: Failed to load magic link token"

I am unable to reproduce it for myself. Any guesses? attached the logs in question

probably related to https://docs.descope.com/flows/conditions/email-scanner

Checking with the user. We'll update here if we find out that's the case

@Amir Wollman is it possible to get a specific "LoginStarted" event cf-ray? I just want to make sure the condition covers your customer's origin aswell. the cf-ray can be found inside the data field if you open the audit log

Sure, @Reuven Zabirov 9cf163a12d2dfdda-IAD

sorry, it does not make sense, the token set in cookies is something that happens after the flow ends. so regardless of what you are doing in flows, it's a project level configuration that is not related to the emailChecker you implementing. we can do a quick call if you have time to discuss.

@Reuven Zabirov What is your availability? We have the same flow in production without the emailChecker that does work. We don't see the "Next" request setting the DSR cookie

i'll be available from 15:30 to 16:30 today

15:30 is great. Where can we book it?

sent an invite