Question on article: AES ERROR - OpeAES ERROR - Open during urgency update failed for assignmentn during urgency update failed for assignment
Hello,
We have been investigating a similar issue.
We found the same error code in logs and did some analysis and found no instances for this class : Assign-Internal.
Would the resolution implied in the article also apply to our issue?
Regards, Tom
***Edited by Moderator Marissa to update platform capability tags****
Rabobank
NL
Offcourse:
Node ID: 354101
SA ID: SA-16327
British Telecom
IN
Hi Tom,
Thanks for the response.
The root cause of the error appeared in the log as below:
This error is due to unneccessary update of open assignments of system flows. Hence, commented them as they are not neccesary for AES(This is the fix provided).
could you please confirm whether you are getting same error in log
Pegasystems Inc.
US
There are no known problems with updating assignment urgency in AES 73. Suggest you upgrade or switch to latest AES version to leverage enhancements and bug-fixes
Rabobank
NL
Hello all, thanks for helping so far, we did some further analysis,
can you confirm this is expacted behaviour:
There is no instances for this class : Assign-Internal.
If YES, does the hotfix change this?
Regards, Tom
Pegasystems Inc.
US
I don't know what the hotfix does. Based on dates, it appears to be for AES 717, which is obsolete. There are no known issues of this sort in the current released AES version, AES 73. Recommendation is for for you to upgrade your AES system to Platform 731 / AES 73. If problem persists after upgrade, open a support ticket. If you are unable to maintain your AES infrastructure and keep it current, consider using the PDC service instead of AES. With the PDC service, Pega is responsible for maintenance and operations, and regularly enhances the software to improve advice, accuracy, capabilities and keep current with Pega platform.