Data Sync For Related Actions Error(While Updating The Data)

There's something weird in that XSD - it looks like all of your "columnDefinition" properties are actually showing as "columnDeTESTition". Can you try to update those and re-upload the XSD? I'd be curious if when you try to write data if the issue is resolved.

You'll likely need to re-sync manually before testing the immediate sync again. If that still doesn't work, can you post the app server log from the time you triggered the immediate sync? The snippet above looks like it's for when you tried to query the synced data, but the issue likely occurred on sync instead of on query.

Thanks for the reply,

The CDT has been corrected and the issue is still raising

Please Find the attachments for error logs and CDT information Below

It's worth checking the setup of your primary key column. Has it been set to UNSIGNED for example? I would suggest testing it with a datatype of INT instead of BIGINT.

I would also review any user filters and the list view for any unmapped columns or links if you have been modifying the record type i.e. look for examples of the annotation being 'exploded' to it's guid. I haven't seen the latter suggestion affect sync but it can cause issues on deployment so who knows.

Given the error message in the logs, I'd suggest opening a support case.

Thanks a lot 

Yes it is working for INT. But it is not working with BIGINT?.But my requirement is to for BIGINT also

For what it's worth (6 months later):

I recently ran into this exact error message (which is still undocumented on the Appian Documentation page: docs.appian.com/suite/help/21.4/Records_Monitoring_Details.html#other-sync-errors) and scenario (writes to DSE consistently caused Record Type's data sync to fail, evem 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.

Any ideas why the use of UNSIGNED on a PK would cause such an issue with Data Sync?

No idea why it is returning error Joseph DeLong

Peter Lewis

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?

NOTE: 

the source table do not have any integer field. it is all text. Even the primary key is a text value (composite key). The sync is failing when using smart service and that too not always. But it IS WORKING in Dev and test env. It is NOT working in PROD env only.

Can there be some other issue that can cause this error randomly in PROD only.
again, Manual and scheduled sync is working fine only smart service sync is failing randomly. In dev and test all three types of sync is working absolutely fine

Ah it looks like you have more info in this post - what do you mean when you say that the primary key is a composite key? It isn't possible to use a composite key with synced record types. In general I still think your best approach is to open a support ticket.

composite key is also a primary key, but the difference is that it is made by the combination of more than one column to identify the particular row in the table. 

Just wanted to add one more info, we have done SAP integration through which we are sourcing data in the record.