Hi there @peterfodor,
Thanks for the question and I hope I’m understanding your methods correctly.
Unfortunately, this is expected behavior when double optin is enabled. Since only one double optin email gets sent despite having two POST calls to subscribe, you will receive the double optin email only for the 1st request. Any updates you make on the profile will not go through until the double optin email is accepted.
On an additional note, you will not need to make a PUT request with the Profiles API. By default, making a POST request to the /subscribe endpoint will update the existing profile by overwriting the values of existing properties with the new ones.
An idea that could be worth exploring is, instead of sending two subscribe requests, you could send only one request at the end of the 2nd step regardless of whether or not the 2nd step has been submitted. If it is submitted, then great - include the name in the request as well as the email address. If it hasn't been submitted and a certain amount of time has passed - then just send the request with the email address only.
I would try the alternative and see if that works for you.
Thank you!
Alex