If needed, you can temporarily suspend the Organization Sync connection between your primary and secondary Salesforce organizations. Before suspending the connection, take a moment to learn how the process works.
|Available in: Enterprise, Performance, Unlimited, and Developer Editions|
- When should I suspend the connection?
- Here are some reasons you may want to suspend the connection:
- You’re experiencing a very high volume of sync failures, and need to diagnose and correct the issue.
- You need to make significant changes in one or both organizations that will prevent data from syncing successfully.
- How does suspending the connection affect users?
- For most users, nothing changes when the connection is suspended. Users with the “Manage Connections” permission will notice some changes on the detail page for the Organization Sync connection:
In addition, the Connection Owner and the user who suspended the connection receive an email twice per day that provides the number of events in the queue.
- A Resume button appears in place of the Suspend button.
- The Connection History log shows a recent Connection Admin Suspended event.
- The Connection Owner field and the options to sync metadata, users, and audit fields are updateable, but updates aren’t sent to the linked organization until the connection is resumed.
- Depending on how long the connection has been suspended, the queue may contain more updates than usual.
- The Published Objects and Subscribed Objects related lists are hidden.
- What happens when the connection is suspended?
- All updates made while the connection is suspended are added to the Organization Sync Record Queue. Queued updates aren’t sent to the linked organization until the connection is resumed.
As the queue fills up, it’ll take longer to get your two organizations back in sync. To minimize syncing issues, resume the connection as soon as possible.