Question
Cognizant
IN
Last activity: 26 Aug 2020 8:17 EDT
Connect rest wizard failed
Hi ,
while running connect rest its failing at the generate recors steps with the below error:
The Flow Action post-processing activity pxGenerateRules failed: Problem invoking function: pega_rules_utilities.getWorstMessage--(PublicAPI), com.pegarules.generated.getWorstMessage_071017_CKPNrhNFy3FhrSNXnnpeLg.
Kindly assist if u guys have any solution.
***Updated by Moderator: Marissa to update categories***
***Updated by moderator: Lochan to add SR details***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
Hi Aditya,
I could see that SR-B10944 is raised for this issue and the issue is resolved automatically after server re-start.
Regards,
Sudhish OP
Pegasystems Inc.
US
Does the stack trace show pyInvokeRestConnector is in play? This could be an issue during Data Page error handling (see PDN article https://docs-previous.pega.com/data-source-error-handling-data-pages).
Cognizant
IN
Hi Paul thanks for the info,but i cant see pyInvokeRestConnector is in play in stack trace,also i am not creating any data layer,might be the rest url issue any suggestion would be great.
Pegasystems Inc.
IN
Hi Aditya,
if you are generating rules from rest wizard, pyinvokerestConnector will not be in the trace.
If you have full stack trace, post here.
on the tracer when generating the rules.
Cognizant
IN
Hi Pylaa,
I checked in the stack trace also,pfa the stack trace.
Kindly share the information if u find any solution for the issue.
PEG
IN
Please refer https://collaborate.pega.com/question/connect-rest-wizard-step-4generate-records-fails-prpc-717
Cognizant
IN
Hi Gangababu,
Thanks for the link but my issue is different as u can see the error message and i am useing pega 7.2 version.
PEG
IN
Could you please share screenshots in detail and also the PegaRules log when issue occurred?
Accepted Solution
Pegasystems Inc.
IN
Hi Aditya,
I could see that SR-B10944 is raised for this issue and the issue is resolved automatically after server re-start.
Regards,
Sudhish OP