The login credentials for every challenge and mission exercise are found on the challenge or mission exercise page in the Scenario section.

These errors indicate the Peg instance has expired or is in hibernate mode. Always access the Pega instance from the challenge or mission exercise page. If the Pega instance is in hibernate mode, a Wake Pega instance button will display. If the Pega instance has expired, an Initialize Pega instance button will display.

Below are the expiration guidelines for each environment:

Challenges

• Inactive Challenge environments will be terminated after 2 days
• All Challenge environments will be terminated after 7 days (regardless of your activity)

These errors indicate a connection to the Pega instance could not be established correctly. The root cause of the issue is usually on the users' end.

Common causes include:

• If you are using WiFi, the WiFi signal may be too weak to reach your device. Check the strength of the WiFi signal. If the WiFi signal is weak, try using a wired network connection.
• Your Internet service provider is having network issues. Sometimes the Internet service to the home has a bad connection which can then cause unreliable service.
• The browser may be experiencing some technical flaws. The issue can be with cache, cookies, or some browser extension you have installed. This issue is seen with all major browsers like Chrome, Mozilla Firefox, Edge, and Safari.

In most cases, this issue resolves itself in short order.

This issue is usually related to the browser you are using - some browsers stop rendering dynamic HTML when there is a pending update for the browser.

The best option is to simply use a different browser.

This error indicates you did not name the case type as specified in the acceptance criteria of the challenge or mission exercise. In most cases, it is best to reset the Pega instance and start over.

It is possible to edit the underlying class name from Dev Studio.

1. Switch to Dev Studio.
2. Click the App explorer, and identify the Work class name (red box), and the case type name (blue box).
   
3. In the header, click Configure > System > Refactor > Classes.
4. Click Rename a Class.
5. In the Old Class Name field, enter the first few characters of the Work class name you identified in step 2, and then press the down arrow on your keyboard to display a list of class names.
6. Select the complete class name that matches the Work class name and the case type name. In this example, you select UPlus-AcctMgmn-Work-BalanceTransferCaseType.
   
7. In the New Class Name field, enter the name of the Work class (do not change) and the case type name as specified in the acceptance criteria of the challenge or mission exercise.
8. Click Next on the next three pages - do not make any changes.
9. On the next page, click Finish.
10. On the next page, click Done.
11. Right-click on the Work class name, and select Refresh all to view the updated class names.

Return to the challenge or mission exercise page and verify your solution.

This error indicates the names of the stages do not match the acceptance criteria specified in the challenge or mission exercise. Spelling errors are the most common cause of this error. Review the acceptance criteria in the challenge or mission exercise and ensure you named the stages as specified in the acceptance criteria.

This error indicates you did not configure the transition of one or more stages in the case life cycle as specified in the acceptance criteria of the challenge or mission exercise.

To resolve this error, review the acceptance criteria for stage transitions in the challenge or mission exercise, and confirm your solution build meets the acceptance criteria.

For remedial learning on how to configure stage transitions, see the Pega Academy topic Case life cycle design: Stage transitions (link opens in a new tab/window.)

This error indicates you did not name a persona according to the acceptance criteria in the challenge or mission exercise. This error can also indicate you did not spell the name of the persona correctly when you first created the persona.

To resolve this error, review the names of the persona in the stage indicated in the task or user story.

If you made an initial mistake when creating the persona:

1. Remove the persona from the stage(s) in the case type, and then save the changes to the case type.
2. From the App Studio explorer panel, click Users > User management.
3. On the Personas tab, delete the persona(s) that are causing the error.
4. Click Add to add a new persona.
5. Enter the name of the persona as specified in the acceptance criteria. Ensure you do not make any mistakes.
6. Enter a description, and then click Submit.
7. Return to the case type.
8. In the appropriate stage - as specified in the acceptance criteria - click + Persona and select the persona from the list.
9. Save your changes to the case type.

This error indicates you did not name the data object as specified in the acceptance criteria.

To resolve this error, review the acceptance criteria for the data objects in the challenge or mission exercise. Then, follow the steps below to resolve the error:

1. Access your Pega instance and open App Studio.
2. Click the Data explorer.
3. Identify the data object that you want to delete
4. Click the vertical menu on the far right of the data object row, and click Delete.
5. Follow the procedure in the challenge or mission exercise to create a new data object.

You must complete the mission test, and the mission exercise (if included in the mission) to earn the mission badge.

Mission progress cannot be reset