You are here:
Lightning Sync Transactions
Review the transactions made by Lightning Sync in response to the work your users complete in Salesforce, and the order in which they occur.
Lightning Sync initiates communication between Salesforce and your mail service asynchronously, so that the sync process doesn’t slow down the users’ intended Salesforce transaction.
- Changes made from Salesforce are queued for transmission to the email service.
- Changes made from the email service are retrieved by a periodic polling mechanism.
When contacts or events are synced to the opposite system, Lightning Sync impersonates the user who created or updated the original item. This behavior preserves accurate data on the items’ last update.
For specific transaction details, review these scenarios.
Sync Contacts from Salesforce to Email Service
- User creates a contact.
- Asynchronous job is enqueued to sync the transaction. Lightning Sync:
- Determines which users who are configured for sync should sync the contact.
- Checks whether contact meets sync filters.
- Calls the email service to see whether the contact exists.
- If it does exist, the contact is updated in the email service.
- If the contact doesn’t exist, Lightning Sync calls the email service to create the contact.
- Matching contacts are mapped between Salesforce and the email service for future syncing.
Sync Events from Salesforce to Email Service
- User creates an event.
- Lightning Sync checks whether the user is set up to sync events.
- Asynchronous job is enqueued to sync the transaction.
- Lightning Sync checks whether the event meets sync filters.
- Lightning Sync calls the email service to see whether the event exists.
- If it does exist, the event is updated in the email service.
- If the event doesn’t exist, Lightning Sync calls the email service to create the event.
- Matching events are mapped between Salesforce and the email service for future syncing.
Sync Event Deletion from Salesforce to Email Service
- User deletes an event.
- Lightning Sync checks whether the record has been mapped to an event in the email service.
- Lightning Sync checks whether the user is set up to have deleted events automatically removed from the other system.
- If mapped to an event, asynchronous job is enqueued. Lightning Sync calls the mail service to delete the event.
Sync Contact or Event Creation, Update, or Deletion from Email Service to Salesforce
Lightning Sync runs a job for all syncing users semi-continuously. The number of syncing users impacts job frequency.
- Lightning Sync checks whether contacts or events were created or updated, or whether events
were deleted from the email service.
- Lightning Sync checks for matched items to update. If items are discovered to have no match, new records are created in Salesforce.
- For deleted events, Lightning Sync checks whether users are set up to have deleted events automatically removed from the opposite system. If so, the event is deleted from Salesforce.
Did this article solve your issue?
Let us know so we can improve!
