Question

APNX-3-1000-030 Record Sync Failure

Forum|Forum|4 years ago
May 3, 2022
11 replies
0 views

v21.4 Cloud

I am getting the below error when updating data of a synced record using a process that has Write to Data Store Entity nodes and Write to Multiple Data Store Entities nodes.

[Appian Work Item - 773428 - execution02 : UnattendedJavaActivityRequest] ERROR com.appiancorp.record.service.RecordReplicaUpdateService - Loading updates to synced record type(s) in ADS failed, invalidated record type(s): [(da0a35ad-c98f-40e7-975c-47ff016a2084,WMS Request)]
com.appiancorp.suiteapi.common.exceptions.AppianException: Unable to sync due to a system failure. Issue identifier: [8d98eb66-d7a7-4786-b881-d48850c684cb] (APNX-1-4521-016)

...
com.appian.data.client.AdsUserInputException: APNX-3-1000-030: Invalid transaction data. Cannot update the same entity multiple times in the same transaction. Invalid id(s): (100218067)

This error is not covered in the docs so unable to find guidance on how to resolve it - docs.appian.com/suite/help/21.4/Records_Monitoring_Details.html#other-sync-errors

Has anyone run into this error? What does "Cannot update the same entity multiple times in the same transaction" mean? I should be able to write or update the Request record how many ever times I want in the process.

Here is a short desc of the data model and the process that updates the synced record:

The data model has 2 synced records - Request and Task - 1:N relationship. The relationship has been setup on both the records
The creation process model of the Request record works fine and both records are immediately synced after the are written to the db
The update process model however causes the immediate sync to fail. The data is updated correctly in the db, no process errors but when I try to open the record I see the record sync failure error message.
The monitoring page for the sync shows that the sync failed (which means the immediate sync) during a "Write to Source" event -
Unable to sync due to a system failure. Issue identifier: [1e56f60d-f25a-43fe-bb1b-c2e9861abd60]

Process Name: <ABC>
Modified Source Rows By Primary Key: 49

richardm900458

Do experience that with all syncs or just with one?

omkara0003Author

Just this one

richardm900458

I think this a such high profile case that you should contact appian support for that

J

josephd0001

For what it's worth (also mentioned under this Discussion, which gave me a hint to the potential underlying issue):

I recently ran into this exact error message and scenario (writes to DSE consistently caused Record Type's data sync to fail, even though the data changes do get persisted, and manually running a data sync has no problems). In my case, the underlying database table's PK was configured as INT UNSIGNED. When I updated it to be simply INT, the data sync errors on DSE writes went away.

I have no idea why the use of UNSIGNED might cause this data sync error, or why Appian might complain about updating "the same entity multiple times in the same transaction", when that's not what was going on.

S

sindhujaj0001

[mention:3e09f462496d489cb01c4c7dea0d44c1:e9ed411860ed4f2ba0265705b8793d05] [mention:c03f69cc9b264af29d5e31ca80c64eff:e9ed411860ed4f2ba0265705b8793d05] [mention:e4a81bed92ad4599b886acee12d98437:e9ed411860ed4f2ba0265705b8793d05]

I am facing similar kind of an issue where the record is sync is failing randomly. We are using record sync smart service in a process model. NOTE: when performing manual sync or scheduled sync then it never fails. It is only failing when using smart service and that too randomly. Few times it is success but few times it fails. There is no defined pattern at times it fails around 300s and at ties it fails within 26s.

We tried checking the stdout logs but there is no clear error message. we have identified few different kind of errors in the logs as below:

Can you please provide any insight/help of what these errors are?

peter.lewis

Employee

I would suggest opening a ticket with Appian support.

P

ponmalars0001

[mention:e4a81bed92ad4599b886acee12d98437:e9ed411860ed4f2ba0265705b8793d05] Is this issue resolved, we are also facing same error. though data got persisted in DB. Sync is failed. Able to do Manual sync successfully.

L

lingeswars903915

I recently ran into the same issue with the same error message in logs.

When inserting a new entry the record sync works fine but while updating the row, the record sync fails. The reason is because we were using BIGINT as the data type of primary key in both database and appian cdt. When converting the BIGINT to INT, the record works fine.

It maybe due to the record doesn't evaluate the integer value as BIGINT even though the datatype mentions the same.