Hi. Following a <recommendation from the AI bot>, ...
# ask-a-descoper
n
Hi. Following a recommendation from the AI bot, we couldn't find something in the React / Next.js Library (AuthProvider, the Descope component, or the flow itself) that would allow us to add a delay before starting the auth flow in order to be able to start the flow directly with an action instead of a screen. Is this something we can do, or should we investigate another approach based on our initial question.
✅ 1
d
Based on the search results, I can see that the documentation doesn't contain specific information about adding delays or starting flows directly with actions instead of screens. Let me provide a response based on what I understand about Descope flows and suggest alternative approaches. Flow Entry Points Descope flows always start with their defined entry point . There's no built-in mechanism to add delays before flow execution or to programmatically skip the initial screen to start directly with an action. Alternative Approaches 1. Flow Design Modification: Restructure your flow to place the action as the first element, followed by any necessary screens. This eliminates the need for a delay. 2. Custom Flow Hooks: Use DescopeFlowHook extensions to customize flow behavior . While hooks don't provide delay functionality, they can modify how screens render and behave. 3. Application-Level Control: Implement the delay in your application code before calling
startFlow()
. Add a timer or loading state in your app, then trigger the flow after your desired delay.
Copy code
// Add delay before starting flow
DispatchQueue.main.asyncAfter(deadline: .now() + 2.0) {
    self.showFlow()
}
The documentation doesn't cover programmatic flow entry point modification or built-in delay mechanisms. I'd recommend restructuring your flow design or implementing the delay at the application level before flow initiation. Flows Overview | Descope Documentation Swift &amp; Python Quickstart | Descope Documentation
m
n
Will take a look, thx
@Meir Wahnon Actually, passkey autofill doesn't fit our needs (it was already enabled and didn't work BTW). Our flow is configured to allow signing in directly with biometrics / passkey or email + password (cf. screenshot 1). We'd like to skip this first screen so the user is automatically signed in using an existing passkey, without having to click on any button (cf. our auth flow attempt in screenshot 2).