Managing your Pega instance
Most frequently asked questions
This issue is caused by security settings on a corporate network or local computer, VPN blocking, geo-locking, or proxy server issues.
If you are on a VPN, try disconnecting from the VPN. If you are on a corporate network or proxy server, it could be the firewall/security settings - try accessing the Pega instance from a different network. You can also try using a different computer if you cannot reconfigure the firewall and other security settings.
This issue is caused by security settings on a corporate network or local computer, VPN blocking, geo-locking, or proxy server issues.
If you are on a VPN, try disconnecting from the VPN. If you are on a corporate network or proxy server, it could be the firewall/security settings - try accessing the Pega instance from a different network. You can also try using a different computer if you cannot reconfigure the firewall and other security settings.
This error indicates the Pega instance has quiesced.
As noted on every challenge and mission exercise page, you must always access the Pega instance from the challenge or mission exercise page. If the Pega instance has quiesced, click the button to power up the Pega instance.
This error indicates you did not use the correct login credentials
The login credentials for every challenge and mission exercise are found on the challenge or mission exercise page in the Scenario section.
This error indicates you did not use the correct login credentials. The login credentials for every challenge and mission exercise are found on the challenge or mission exercise page in the Scenario section.
You can change the user password for a Pega instance.
Use the login credentials detailed in the Scenario section of the challenge or mission exercise.
You cannot change the password for a Pega instance. Use the login credentials provided in the Scenario section of every challenge and mission exercise.
This error indicates the Pega instance has quiesced.
As noted on every challenge and mission exercise page, you must always access the Pega instance from the challenge or mission exercise page. If the Pega instance has quiesced, click the button to power up the Pega instance.
We recommend forcing a browser refresh to ensure the most current state of the Pega instance is displayed. Use Ctrl + R (Windows) or CMD + R (macOS).
Other frequently asked questions
Each Challenge and Mission Exercise uses a separate cloud environment.
You may have only two active systems per mission. If you initiate a third environment in the same mission, your oldest environment will be terminated.
The expiration guidelines for Pega instances are:
Challenges
- Inactive Challenge environments will be terminated after 2 days
- All Challenge environments will be terminated after 7 days (regardless of your activity)
Mission Exercises
- All Mission Exercise environments will be terminated after 7 days (regardless of your activity)
The login credentials for every challenge and mission exercise are found on the challenge or mission exercise page in the Scenario section.
You cannot recover your work after you reset a Pega instance.
Each Challenge and Mission Exercise uses a separate cloud environment.
You may have only two active systems per mission. If you initiate a third environment in the same mission, your oldest environment will be terminated.
The expiration guidelines for Pega instances are:
Challenges
- Inactive Challenge environments will be terminated after 2 days
- All Challenge environments will be terminated after 7 days (regardless of your activity)
Mission Exercises
- All Mission Exercise environments will be terminated after 7 days (regardless of your activity)
To reset a Pega instance and start the challenge or mission exercise over, navigate to the challenge or mission exercise page, then click Reset Pega Instance.
The ERR_CONNECTION_RESET error often occurs because of VPN, firewall, or proxy settings. A VPN or proxy server may be blocking the internet connection to a particular site.
If you are on a VPN, try disconnecting from the VPN. If you are on a corporate network or proxy server, it could be the firewall/security settings - try attempting the challenge from a different network.
This issue is usually caused by a slow network connection or a VPN. If you are connected to a VPN, try disconnecting from the VPN.
We also recommend using a different browser.
This error indicates a temporary service disruption with your Pega instance.
We recommend waiting a few minutes before trying to access your Pega instance.
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 that your Pega instance may be quiesced, or is no longer available.
Always access the Pega instance from the challenge or mission exercise page.
To reset a Pega instance and start the challenge or mission exercise over, simply click Reset Pega Instance.
If you are having technical issues with a Pega instance, please contact the Pega Academy support team.