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

Resource Not Found Error for REST Service



Post Pega 7.3.1 update, the Service-REST rule is saved to a higher ruleset version and the Service-REST call from an external client works correctly. However, error occurs on restricting the ruleset version in the application definition rule from using the previous version of the Service-REST rule.

Error Messages

Resource Not Found

Steps to Reproduce

  1. Create a Service-REST rule in Pega 7.3.
  2. Export the application and import it to Pega 7.3.1. Save the Service-REST rule migrated from Pega 7.3 to a higher ruleset version in Pega 7.3.1.
  3. Call the Service-REST using SOAP UI. The Service Call works correctly.
  4. Edit the application definition rule to restrict the ruleset version such that the previous version of the Service-REST rule (prior to saving the rule to a higher ruleset version) is used.
  5. Call the Service-REST using SOAP UI. The service call fails with 'Resource not found' exception.

Root Cause

This behavior is as per Pega product design.


Follow the instructions for the 'Service REST rule resolution' and 'New rule precedence' sections provided in the following article:

Published May 7, 2019 - 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