topic Re: Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services in Developers Questions https://community.esri.com/t5/developers-questions/scripting-replication-and-synchronization-workflow/m-p/121477#M769 <HTML><HEAD></HEAD><BODY><P>I believe we resolved the issue.&nbsp; After realizing that we had published two geodata services that referenced the same enterprise geodatabase version connection file, we removed one of the services from the ArcGIS Server site.&nbsp; Now when creating and editing a checkout replica, all of the edits are immediately synchronized to the SDE.Production version and available in the next round of replication.&nbsp; There is no synchronization delay that appeared to be occurring in the background.&nbsp;&nbsp;</P><P></P><P>Hopefully this helps anyone else that is having&nbsp;issues with ArcGIS Server and checkout replicas!</P></BODY></HTML> Fri, 28 Jun 2019 12:59:30 GMT AdamG 2019-06-28T12:59:30Z Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services https://community.esri.com/t5/developers-questions/scripting-replication-and-synchronization-workflow/m-p/121476#M768 <HTML><HEAD></HEAD><BODY><P style="background-color: #ffffff; border: 0px;">Our organization is currently using one instance of ArcGIS Server, where we have published a Geodata service that references an SDE connection file.&nbsp; Via a python script we are&nbsp;able to create a check-out replica using the same SDE connection file, edit the features, and check the&nbsp;edits/changes back in to the SDE.Production version.&nbsp; Once the changes have been checked in and synchronized to SDE.Production via another python script, I am able to use ArcMap/Catalog to see that the changes are immediately posted to the SDE.Production version.&nbsp; However, if we attempt to re-create the checkout replica, it does not contain any of these edits that are showing in SDE.Production.&nbsp; It is as if the current state of SDE.Production was never updated and we are replicating it's prior state.</P><P style="background-color: #ffffff; border: 0px;">&nbsp;</P><P style="background-color: #ffffff; border: 0px;">Is there a specific way to synchronize the replicas so that changes are reflecting immediately?&nbsp; Could there be a delay in the edits becoming available for replication?&nbsp; Could this be due to pooling or recycling parameters?&nbsp; Any help would be greatly appreciated.&nbsp; There is next to zero documentation on how to use the ArcGIS Server resources for check out replication.&nbsp;</P><P style="background-color: #ffffff; border: 0px;">&nbsp;</P><P style="background-color: #ffffff; border: 0px;">Thanks!</P></BODY></HTML> Wed, 26 Jun 2019 16:57:18 GMT https://community.esri.com/t5/developers-questions/scripting-replication-and-synchronization-workflow/m-p/121476#M768 AdamG 2019-06-26T16:57:18Z Re: Scripting replication and synchronization workflow with ArcGIS Server and Geodata Services https://community.esri.com/t5/developers-questions/scripting-replication-and-synchronization-workflow/m-p/121477#M769 <HTML><HEAD></HEAD><BODY><P>I believe we resolved the issue.&nbsp; After realizing that we had published two geodata services that referenced the same enterprise geodatabase version connection file, we removed one of the services from the ArcGIS Server site.&nbsp; Now when creating and editing a checkout replica, all of the edits are immediately synchronized to the SDE.Production version and available in the next round of replication.&nbsp; There is no synchronization delay that appeared to be occurring in the background.&nbsp;&nbsp;</P><P></P><P>Hopefully this helps anyone else that is having&nbsp;issues with ArcGIS Server and checkout replicas!</P></BODY></HTML> Fri, 28 Jun 2019 12:59:30 GMT https://community.esri.com/t5/developers-questions/scripting-replication-and-synchronization-workflow/m-p/121477#M769 AdamG 2019-06-28T12:59:30Z