Hey everyone, I’m using a Flow for sign-up/sign-in with magic link and social auth. I’m trying to disable the magic link option because bots are creating multiple accounts. I’ve removed all magic link-related steps from the Flow and saved it successfully, but users are still signing in via magic link. Is there any caching involved? Could a saved Flow with errors still be serving the previous version?

Flow Changes and Caching Flows don't have traditional caching that would cause old versions to persist. When you save a Flow, changes take effect immediately. However, there are a few things to check: Verify Flow Configuration 1. Confirm you're editing the correct Flow that your application is using 2. Check that all magic link actions and screens are completely removed from the Flow 3. Ensure the Flow is properly connected from start to end without broken paths Check Authentication Method Settings Magic link functionality can also be controlled at the authentication method level . Navigate to Settings > Authentication Methods > Magic Link in the Descope console to verify the method isn't enabled globally. Flow Version Issues If users are experiencing version mismatches, this can happen when a Flow has been rendered for some time before interaction . The

restartOnError

flag in client SDKs can help resolve this by restarting the Flow when version conflicts occur. • Check if your Flow has validation errors that might prevent proper deployment • Verify all Flow steps are properly connected to the end step • Test the Flow in the Descope console Flow runner to confirm magic link options are no longer available If magic link authentication is still appearing after removing all related steps and verifying settings, this suggests the issue may be with Flow connectivity or authentication method configuration rather than caching. Magic Link Settings Guide | Descope Documentation Troubleshooting Flows | Descope Documentation Descope Common Errors | Descope Documentation