Troubleshooting the Starter Packs
The following article covers the errors you might encounter when using the starter packs, the reason for the error, the starter pack in which the error occurs, and the resolution to implement. For more information on troubleshooting Pega Platform-related errors, see Troubleshooting Pega services and Support Guide.
| Error code/error message | Starter pack | Reason | Resolution |
|---|---|---|---|
| 401 | All | Mismatching authentication type between the Infinity server configuration and the starter pack application configuration. | Ensure that the authentication type is set correctly. Follow the instructions in the configuration-related documentation in the starter pack. |
500
Failed to generate com.pegarules.generated.html_harness.ra_action_confirm | All | This is a DX API-related error and occurs when the application is not compliant with the DX API or has non-DX API UI. This error is most likely to occur in Submit-related screens. | Ensure that the application is DX API compliant. You can override the portion of the OTB application rules that are not compliant with the DX API, or change application-specific UI. To debug DX API errors, follow the procedures outlined in Debugging DX API. For more information about features supported by the Starter Pack, see Supported Features. |
| Assignment <assignment ID> cannot be opened | Angular | The application is unable to open the specified assignment. |
|
| ERR_SSL_PROTOCOL_ERROR | All | This issue occurs when using the Google Chrome browser and the local front-end server is configured with HTTP. Due to Google Chrome’s domain security policies, the browser automatically redirects to the HTTPS protocol. | Modify Google Chrome’s domain security policies to ignore localhost:
|
| Failed to compile | React | Incompatible version of React scripts. | Set the version of React scripts to the version specified in the starter pack. The latest React starter pack is meant to be using 4.0.3. |
| Incorrect password | All | Invalid or incorrect password. |
|
| Network error (CORS error) | React Vue | The endpoint URL (PEGAURL or BASEURL) path in the endpoint file is not configured correctly, typically missing the /api/v1 part. | The browser displays Network error only, open the browser's Network tab for the endpoint to view the exact error. Ensure that the PEGAURL or BASEURL path is in the correct format: <pega server path to servlet>/api/v1 |
| Network error (blocked:mixed-content) | React Vue | The endpoint URL (PEGAURL or BASEURL) in the endpoint file is configured to use http:.. but you are trying to start a local server instance using the npm run starthttps command. | The browser displays Network error only, open the browser's Network tab for the endpoint to view the exact error. Use the |
| Network error (failed) | React Vue | The connection to the configured server is incorrect. | The browser displays Network error only, open the browser's Network tab for the endpoint to view the exact error.
|
| No next action to go to | Angular | The GetNext call did not return any action. | Ensure that the GetNext call is correctly configured with a supported action. |
| Pega_API_022: Use of TLS/SSL is required | All | The endpoint URL (PEGAURL or BASEURL) path in the endpoint file is configured to use http:.. but the service package is configured to use TLS/SSL. | Update the path to use https:.. |
| Unsupported action | Angular | The action set is not supported. | Ensure that the action set to use is supported by the starter pack. For more information about supported features, see Supported features. |
| Your account has been disabled, contact your system administrator | All | Application's operators are disabled. | The imported application's operators are disabled by default. For more information to enable operators, see the Troubleshooting section in CableConnect (sample application). |
Previous topic Technical operator