Skip to main content
3 answers
  1. Today, 7:17 PM

    Salesforce Support has confirmed that this is a known issue. 

     

    Resolution to complete the challenge: Creating a new Org again from scratch and repeating the steps fixed the issue.

0/9000