Error requesting data from Pega - Code: InternalServerError(500)
We are connecting an RPA with Pega; everything seems to work fine until the RPA completes its work; when returning the info to Pega, we are getting an error on the call to Pega's API.
Code: InternalServerError(500)
On the Pega Logs we can see it is not able to complete the call to the API, I have tried hitting the API manually using the URL Runtime shows and I am able to get info back, but for some reason when called from Robotics Pega does not bring the data.
I am attaching the logs. Runtime error shows at the end of the logs.
Accepted Solution
Prime Therapeutics
US
Pegasystems Inc.
IN
Hello,
Please check if the pyWorkPage of the case is having any error messages(pyErrorMessage). Open the clipboard and check. If you are not seeing pyErrorMessage, Please create a temp activity and call Page-Validate method on the case and see if any validation errors are thrown.
Regards,
Vaspi
Prime Therapeutics
US
@Vaspino errors in pyWorkPage, seems the call from Robotics to pega through the API generates an error and the automation doesn't event change status.
Thanks!
Updated: 28 Jun 2021 22:44 EDT
Pegasystems Inc.
IN
Could you please share screenshot of the audit of the case in Pega. Is the case moved to conflicting Robotic Automation queue
Pegasystems Inc.
IN
Accepted Solution
Prime Therapeutics
US
I found the issue; you were right at trying to look if pyWorkPage had errors, it didn't have any when opening the case, but I traced the REST service this morning and found out that pyWorkPage was triggering some error messages; it seems we had an old property referenced in the case, that property was withdrawn, and it was triggering the errors.
It was curious that the withdrawn property didn't make the whole case crash before, but only when getting the call from the API.
Thanks for the help!
@Vaspi
I found the issue; you were right at trying to look if pyWorkPage had errors, it didn't have any when opening the case, but I traced the REST service this morning and found out that pyWorkPage was triggering some error messages; it seems we had an old property referenced in the case, that property was withdrawn, and it was triggering the errors.
It was curious that the withdrawn property didn't make the whole case crash before, but only when getting the call from the API.
Thanks for the help!