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

No candidates found error when calling function



An activity contains a step to call a custom function. The activity and function were migrated to a higher environment. When the activity is called in the higher environment it fails with a 'No candidates found' error.

Error Messages

No candidates found [possible function name, ruleset/version or number of parameter problem]     for Rule-Utility-Function in ruleset list <null> expected since isEditing is false ruleset = Custom library = CustomUtilities functionName = CustomFunction parameters = []

Steps to Reproduce

  1. Write a custom Rule-Utility-Function.
  2. Write an activity that calls the custom function.
  3. Migrate the activity and function to another environment.

Root Cause

The issue can occur is if the activity calling the function is executed before the function has been imported and compiled.


Resave the calling activity once the function has been imported and compiled.

Published March 23, 2016 - Updated October 8, 2020

Was this useful?

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