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

REST Connector: Incorrect pyStatusValue



In Pega 7.1.4, when user is running a data page to execute the Connect REST rule with an incorrect credential, the pyStatusValue returned is "Fail: Authentication parameters incorrect" as expected. In 7.1.6, the pyStatusValue returned is "Fail:InternalReason"

Error Messages

Error: "Fail:InternalReason"

Steps to Reproduce

Call the Connect REST rule with an invalid login credentials

Root Cause

Some REST APIs return important information in the body or headers, such as "your password has expired," when there is a 401 response code. Starting in PRPC 7.1.6, by default, we no longer avoid consuming the body and headers in order to provide details about the failure.


Avoid consuming the body and headers when there is a 401 response code by creating the following Dynamic System Settings.
 Owning Ruleset: "Pega-IntegrationEngine"
 Purpose: "http/LegacyResponseMapping"
 value: "true"

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% 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