Onboarding: display a clear message/CTA when website creation process fails

[Robertght]

Quick summary

Coming from here and pfYzsZ-45-p2 I'm opening this report separately.

Steps to reproduce

N/A

@ellatrix if you remember more about this and what steps we can take to replicate, please edit this section.

What you expected to happen

To see a button to refresh or a message that the website creation process failed.

What actually happened

The screen remained stuck on loading with errors in the browser console:

Impact

One

Available workarounds?

No and the platform is unusable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

[jartes]

📌 REPRODUCTION RESULTS

• Could Not Replicate

📌 FINDINGS/SCREENSHOTS/VIDEO

• After following the steps on pfYzsZ-45-p2 I was not able to get the error.

📌 ACTIONS

• Leaving as In Triage waiting for reproduction steps.
• Lowering priority from High to Low.

[tanjoymor]

While I'm not sure about steps to reproduce, I can confirm that I have randomly run into this during other testing processes.

@paulopmt1 would you say this is related to what we ran into during the Quake plugin walk through?

It's also similar to what I ran into and commented on here: #96513 (comment)

Not sure what next steps should be here.

[paulopmt1]

would you say this is related to what we ran into during the Quake plugin walk through?
Could Not Replicate

By looking at the image, both https://doubleclick.net/ and public-api.wordpress.com were unreachable by the user, which indicates they had a network connection error during that process. Since these resources are from two different companies, this seem to be related to the user end.

After understanding the flow and a few attempts to reproduce the issue, I found that if the /onboarding-customation route fails for any reason, we end up in this infinite loading screen. This is the code responsible for it.

To fix it, we need to handle that Promisse.all failure event so we can either try it again, or show a retry button to the user so the window.location.assign will be called as expected.

Here's a video showing how I simulated the bug: pfYzsZ-45-p2#comment-963
(I basically renamed that /onboarding-customation request so our API returned an invalid path).