We are sharing data between two Salesforce orgs (Org1 & Org2) using S2S on a custom object called Shared__c with fields Name and Shared_Field__c. Both orgs are set up to publish the Shared__c object and the fields Name and Shared_Field__c to the other org. Additionally both orgs are subscribed and auto-accept the Shared__c object from the other org and map the Name and Shared_Field__c fields to the Name and Shared_Field__c fields in their org.
When a new Shared__c record is created in Org1 with Name="Test" and Shared_Field__c="New" a record is also created in Org2 with Name="Test" and Shared_Field__c="New" as expected. Additionally when we update Shared_Field__c="In Progress" in Org2 we see that Shared_Field__c="In Progress" on the related record in Org1. All of this is as expected.
However occasionally when we update Shared_Field__c to a new value in Org2 the update isn't reflected in Org1. When this occurs I can update Name="Test2" save the record, set it back to Name="Test" in Org2 and then look back at Org1 and see the update to Shared_Field__c is now reflected in Org1.
Note there are data validation rules in Org1 on the Valid__c field of the Shared__c record. However the Valid__c field is not being changed after the record is created so that seems like it would be a non-issue.
I am at a loss as to what is causing this intermittent failure to push updates from Org2 to Org1. Ensuring the data in Org1 and Org2 is critical. Aside from setting up a field called Bogus__c on Shared_Field__c and setting up a Scheduled Apex job to update Bogus__c on a nightly basis I am at a loss for a way to ensure the data is in sync.
We opened a case with Salesforce Support over a year ago and they not only haven't been able to identify the cause but they have also often been unresponsive.
I am wondering if anyone else in the community has experienced S2S intermittently not sharing data. If so were you able to identify the cause of the failures?
Any insight would be greatly appreciated. Thanks!