Question
Receiving this error "[@baseclass.pyMessageLabel]AssignmentCorrupted" in trace without more details
Hi Team,
Can someone help me with the below. I was trying to proceed further by clicking next on the assignment. And i get to see the below without much information.
A processing error has occurred
Object key **************************
This assignment has been corrupted and processing cannot proceed.
I see the below error in Trace on pyWorkPage in Pega OOTB activity(Work-setOutput) without any other information(checked in logs as well).
[@baseclass.pyMessageLabel]AssignmentCorrupted
Throw some light on what could be the possible reasons for the above.
Regards,
Theja
Hi Mike,
Thanks a lot for the response. I'm able to see the newAssignPage on the tracer. Attached the screenshot.
Since this application is on Cloud, We don't have access to the database to further debug.
To be more precise with this issue, We are able to proceed with this request further in normal scenario. We have a scenario where we can create a vendor before proceeding with the assignment. So, When we try to create a new vendor(which seems to be working good) within the request, we are unable to proceed further with the above assignment corrupted.
We are creating vendor with this utility - 'createWorkProcess' before proceeding with the assignment.
Regards,
Theja
Hi Theja,
The good news is both objects exist in the trace. The next step is to open up the newAssignPage and compare it to the contents of the pxFlow page. Do they match up? Also, that doesn't appear to be a trace of the error. What is the page that it fails on? Is it the newAssignPage for the new assignment?
Thanks,
Mike
Hi Mike,
I did check both newAssignPage and pxFlow page. But It doesnt give me much info. Attached the details for your reference.
That is where I'm confused,as I couldn't find the the page it is failing on trace. It directly brings the pyWorkPage and the error on it. Hope the attached helps. Thanks much!
Regards,
Theja
Hello,
I'm not familiar with that error message. I would start by comparing the data on the newAssignPage and the corresponding pxFlow page. Do they disagree? Are you unable to open the newAssignPage? Does the assignment exist in the database? My guess is that you can't open the assignment, object, but that one exists in the database (because otherwise you'd be getting a flow removed, or flow not at task type error or one saying the assignment doesn't exist). From there, I'd look at the assignment in the DB. Does it appear corrupt? If you create an activity that does an obj-open-by-handle passing in the assignment key, does it load into the clipboard or give you an error? What error do you get?
Thanks,
Mike