This article provides details about the impact of different actions that stop the synchronization process.
Ways to Stop the Synchronization
Synchronization stops because of the following reasons:
- Deactivated Connection
If the Connection has been deactivated at either end. - Unexalate Operation
The entity has been Unexalated, i.e further synchronization has been stopped. - Clean-up Tools
The synchronization has been stopped either for a particular entity or for a Connection. - Uninstalled Exalate App
The Exalate App has been uninstalled. - An Entity Under Sync is Deleted
Below you will find a detailed description of how these actions affect entities that have been synced.
Impact on the Entity if the Synchronization is Stopped
Deactivated Connection
Impact: The entities will remain on both sides keeping the data they've already exchanged. The link between these entities will remain untouched.
You can later resume the sync from the moment it has been stopped.
Unexalate Operation
Impact: The entities will remain on both sides keeping the data they've already exchanged. But the link between these entities will be removed.
Clean-up Tools
Impact: The entities will remain on both sides keeping the data they've already exchanged. But the link between these entities will be removed.
Uninstalled Exalate App
Impact: Exalate does not remove the configuration data after uninstallation.
If you uninstall the app, synchronization will stop, but the other side will throw errors. It does not affect the entity data though.
Exalate does not remove entity information, received during the active synchronization.
By default, when you reinstall or re-enable the application again, the synchronization will be resumed from the point it has been stopped.
An Entity Under Sync is Deleted
Impact: When you delete an entity, Exalate considers it as a synchronization event. It ensures that future entity updates are not synced.
The synchronization panel will indicate that the remote entity has been removed.