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

UnresolvedAssemblyError occur when calling Function Rule



As application is utilizing a Function rule. The function is correctly implemented and compiles without error. However, at runtime the Function fails to invoke via a DataTransform with UnresolvedAssemblyError.

Error Messages

2016-01-28 09:52:32,457 [.PRPCWorkManager : 7] [ STANDARD] [ myApp:0x.0y.0z] ( FlowProblems.Work_.Action) ERROR - Problem flow abort due to system flow FlowProblems being the issue The flow SendToCreditDepartment had a problem on step Integrator2 of: ** 2001449583§a_function§PegaEL-InvalidExpression    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 = a_ruleset library = a_Library functionName = a_function parameters = [ Item: param.PackageName Pega type = text Java data type = String]    @(a_ruleset:a_Library).a_function(param.PackageName
From: (B1DB4FA2881D8843B0A39D2E340F51056) 
at com.pegarules.generated.activity.ra_action_problemflowthrowexception_0287af95244464eee8a78ef088ca28e4.step3_circum0(
at com.pegarules.generated.activity.ra_action_problemflowthrowexception_0287af95244464eee8a78ef088ca28e4.perform( 
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( 
at com.pegarules.generated.flow.ra_action_flowproblems_082e122ca3ac7453c435359f419716bd.RunTaskActivity(

Steps to Reproduce

Not applicable.

Root Cause

The UnresolvedAssemblyError associated to a Function rule can be a cache related issue.

However, there is an additional known condition in which the error can occur. There are situations where the Function name signatures not normalized correctly and when that occurs, the system will unable to locate the Function rule and the error of UnresolvedAssemblyError occur will get thrown. 


To rule out any caching issue, try the Revalidate and Save operation and clear the contents in PegaTemp directory. If the issue still persists, install HFix-25979 which contains an updated version of The fix ensures the Function name signature getting normalized and located as expected.  


Published February 13, 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