Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

HTTP 500 internal server error



HTTP 500 internal server error occurs due to pzIncludeMashupScript. Core engine does not return pzIncludeMashupScript when required during the launch of mashup. The pzIncludeMashupScript does not require authorization for access.

Error Messages

HTTP 500 internal server error

Steps to Reproduce

Log out from the mashup and relogin. The error occurs when the mashup is relaunched.

Root Cause

A button which loaded in the application was configured to log out from the Pega application. Clicking the button invoked a local Javascript function which invoked the @baseclass.LogOff activity. However, it did not clear the web sockets. Hence, an API call was triggered with the Unsubscribe push activity on opening the Pega application.


Perform the following local-change:
Add window.msgMgrUniqueId=undefined; to the Javascript function.



Published May 22, 2019 - Updated October 8, 2020

Was this useful?

66% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us