Hi all- recently did an auth flow switch from magi...
# ask-a-descoper
m
Hi all- recently did an auth flow switch from magic link to OTP and the dashboard is showing a massive increase in errors. (User complaints have been low though.) Is this just because of cached data that directs folks to old flow (I have a redirect but it still pulled some errors in the logs-especially over the first 72 hours.)
✅ 1
d
Error Spike Analysis Your error increase is likely expected behavior during the magic link to OTP transition. The Flow Analytics dashboard shows step-by-step visibility into authentication journeys and can help identify where users are dropping off during flow changes. Common Causes During Flow Switches 1. Cached browser data - Users with bookmarked magic link URLs or cached authentication states will hit the old flow endpoints 2. Redirect handling - Your redirect implementation may generate logged errors even when working correctly 3. Session state conflicts - Existing sessions expecting magic link tokens encounter OTP validation instead Monitoring Recommendations • Check the Flow Analytics dashboard to see where users are exiting in your new OTP flow • Review error handling configuration in your flow actions to ensure graceful fallbacks • Monitor the 72-hour window you mentioned - cached data typically expires within this timeframe The low user complaints suggest your redirect is working properly for the user experience, while the dashboard captures technical errors from the transition period. Descope Project Dashboards: Clear Visibility for Modern CIAM Descope Project Dashboards | Descope Documentation Actions Overview | Descope Documentation
c
Hey @Max Burns what's the project ID? I can check on our backend
m
P2fYs52LoB3Po48CcWl3XkgBw8z5
Thanks, chris!
c
Also worth looking at the troubleshooting page for any increase in errors around sending OTP/etc https://app.descope.com/audits/tlogs But taking a look at the backend, give me a min
m
Yep, been monitoring that. Just noticed the spike on the dashboard tho and was alarmed
c
Looks like you left something dangling in the flow when you added OTP. Let me pull it down and take a look, but looks like after you verify the OTP, it has no next tast to get to.
m
oh, weird, is it the verfiy OTP choose another auth node?
c
image.png
It's this one actually.
m
yep- shoot. how do i fix?
c
Either delete that choose another button or send the user back to the beginning of the flow
m
Is one resolution preferred over other? Seems like sending back is easiest so ill probably do that
c
Baker's choice, but since you don't have another method, I'd just delete that button.
You can edit the screen and
m
right, of course... done!
Thank YOU!
Hey Chris, if you're around today, just following up on this. Our error rates are still high but users complaints are low. Is this from cached data in users browsers from the old flow?
@Chris Carper
c
Hey Max - for the last 2 days I see 500 or so errors on the project. 120 are on the rate limit action - so essentially users are repeatedly trying to send the OTP it looks like. The rest are either too many attempts or invalid. What kind of complaints are you receiving from users? CC: @Akash Jivane as I will be unavailable for the next several hours (PRID: P2fYs52LoB3Po48CcWl3XkgBw8z5)
m
Yeah, that just seems pretty high.
Complaints are mainly the usual "I can't log in" with the new addition of "I see a blank screen" (when redirected from Libby) and asking folks to reset their browser/ clear their cookies and cache has done the trick. So I was thinking it was data stored from the old flow interfering with new sign on requests, but the error bar is just off the charts!
But! Even those complaints are pretty low, only seeing a handful each week