In the Step 2 you are making changes to the user.
The step 3 (Assign a temp password to a user) needs a user.
So in the Step 3, in the field “User”, instead of making a Search, just reference the result of the Step 2.
Changing the third step and referencing the user to the second step does not change the outcome.
In order to identify the user (it’s a signup confirmation page) the UID has to be retrieved from the URL. The URL should come from the email.
But in the URL the UID is missing (as I stated in my first message).
Ok, so, the information that the second action is actually not working makes sense for me. As I already presumed. That is why referencing the second step will not change the outcome. The second step is also not finding any user.
When you check the option to “Send an email to confirm the email” Bubble will handle all the process. Clicking in the link received in the email, your user will be redirected to the confirmation page provided by you (in your case email_confirmation) and his e-mail will be automatically confirmed and the data field called “email_confirmed” (inside your User) will change to YES.
So, in the end, you don’t need to create a data field called “verification”. You can use the already built field called “email_confirmed”.
This field (email confirmed) does not exist as a field of User datatype that you can play with but when you try to access it as Current User from any page it is there. I am sure Bubble has its reason to hide it from the data tab.