Hi @rp_st , even when i resend code , then also i am able to use the old code and get success respose , but ideally this should not be the case. Any specific reason why its happening

hey @anurag06557 this is expected. Cause for email / sms delivery, the code delivery order is not defined by when you called createcode or resend code. So for better UX, it behaves this way. But once you consume a code, all codes that were sent are removed.

is there any thing we could do to avoid this behaviour

you can customise how our functions work. You can override the resendCodeAPI on the backend, and then before calling the original implementation, you can get a list of all codes sent using the preAuthSessionId (this value is in the input to the function), and then call revokeCode on each of those codes.

ok

search for resendCodePOST

Hi @rp_st

apis: (originalImplementation) => {
        return{
          ...originalImplementation,
          resendCodePOST: async(input)=>{
            // console.log(input)
            const preAuthSessionId = input.preAuthSessionId
            const oldCodes = await listCodesByPreAuthSessionId({preAuthSessionId, tenantId:'public'})
            console.log({oldCodes})
            if(oldCodes?.codes.length > 0){
              for await(const code of oldCodes?.codes){
                console.log(code)
                await revokeCode({codeId:code.codeId, tenantId: 'public'})
              }
            }
            const newCOde = await originalImplementation.resendCodePOST(input)
            console.log({newCOde})
            return newCOde
          }
        };
      },

every time in the newCode response i am getting restartFLowError, why so

@porcellus , any idea why this is happening?

if you revoke all codes of a device (or preAuthSessionId) the device will be deleted, so you can't resend it

ok, trying

happy to help 🙂