/passwordless/start returns 200 when Custom phone provider action throws an error

When custom phone provider provider action under Brand->Phone provider fails, /passwordless/start API that is invoked by the Auth0PasswordlessLock widget returns 200 (OK). Hence there is no error displayed to the user even when though sending the SMS failed.

Is this is a known issue?

Hi @administrator2

Welcome to the Auth0 Community!

Reading through the information provided, the returned 200 response indicates that the API is correctly called and there should not be any issues on the Auth0 side, meaning something happens on the provider’s end that prevents the SMS from being sent.

I would recommend implementing some console.logs within the Action to check what information is being sent. Multiple issues could occur, from the message being blank/non existent, to the sender’s or recipient’s phone number ( from and to ) being incorrect, or there might be restrictions when it comes to the destination’s country/network.

Console.logging might help pin-point the issue, where something is expected to be sent, but it is not.

Please let us know if you find anything else that could help with determining the exact issue. As you receive a 200 code, the logs of your tenant will most likely not show anything useful in this case.

I will leave some documentations here as well, in case they come in handy:

Have a great one!
Gerald