Pega API [POST] is creating a case even if there was an error in the transaction
Pega API 7.2 is being used to create cases and sometimes the response is an error, however, case gets created. This behaviour is causing duplicated cases from the business side since when the error is returned, the external system recalls. Pega is deployed in a cluster and what we have noticed is that this error only occurs in cluster.
Error returned is: Pega_API_014: .pyCommitError: ** ** ORA-00001: unique constraint (DATAADM.PC_HISTORY_CCC_NN_YY_WORK_PK) violated
Is there any mechanism to avoid creating the case when an error is returned?
***Edited by Moderator: Pallavi to update platform capability tags***
PEG
PL
When you are creating a case, is there any explicit commit. As far as i know, pega maintains the transaction and if the error occurs, pega dont create a case. Either the finish assignment is called and the case is created or some commit is there before error occurs.
To avoid this, you can create a transient case and persists when everything is good.
More detailed usecase and some screenshots will give more idea into the error and how to avoid it.
Accenture
SG
Hi Jose,
This is probably one of the input value in the case is not supported by its type in the DB.
I have faced similar issue when I am writing a case with improper Case ID and trying to commit it to DB. However, the error will show on the next case creation instead of on the current case creation.
I suggest to verify a scenario, try creating case with irrelevant data and after that create new one with proper data. The same exception will show for the second case.