Keep Your Development Environment in Sync

Use back sync to update your development environment with the latest changes from the first pipeline stage. Keeping your environment current helps maintain compatibility with your team’s changes and reduce merge conflicts.

Required Editions

Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions
Not Available in: Government Cloud Plus. Contact your Salesforce account executive for more details.
Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. Lifecycle Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions.

Lifecycle Center tracks which work items were promoted to the first pipeline stage but aren’t yet deployed to your development environment. You can see exactly what’s missing before you sync. When you connect a work item to a development environment, Lifecycle Center notifies you if the environment is out of sync. Run back sync when you begin work or at regular intervals to keep your development environment current.

Choose a Back Sync Deployment Type

When you start a back sync, select the changes to deploy to your development environment.

  • Partial deploy: Deploys only the changes from work items that were promoted to the first pipeline stage but are missing from your development environment. This delta sync is the fastest way to catch up, because it deploys only the changes that you don't already have.
  • Full deploy: Deploys all changes from the first pipeline stage branch to your development environment. Select this option if your deployments are failing due to dependent or missing metadata.

Considerations Before Back Sync

Before the back sync runs, Lifecycle Center checks the status of every work item associated with the development environment. If any work item has a status of In Progress, In Review, or Ready to Promote, Lifecycle Center blocks the sync. Commit and promote those work items, and then run the sync.

Warning
Warning Back sync overwrites unpromoted changes in your development environment. Before you proceed, make sure that your environment doesn't contain any changes that you want to keep.
  • Run Back Sync
    Move changes from the first pipeline stage to your development environment. Running a back sync makes sure that you're working with the most up-to-date, approved changes.