After a Developer or Developer Pro sandbox refreshes or a scratch org expires, the
connection to DevOps Center becomes unusable. Replace the development environment in the
next-generation DevOps Center to restore the connection. DevOps Center deploys the pipeline stage
branch to the new sandbox so that you can continue working with the correct metadata and
configuration data.
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. DevOps Center
is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms
and conditions.
User Permissions Needed
To replace an environment:
DevOps Center Admin
To access the named credentials required to authenticate to the environment:
Access DevOps Center Named Credentials
Important We recommend refreshing sandboxes from the production (release)
environment, or cloning them from a pipeline stage or an existing development environment.
Before you replace a development environment, review the considerations, and make sure that the
new development environment has source tracking enabled. See Replace and Connect a New Environment.
Note In DevOps Center (Managed Package), this operation is called swap environment.
Go to the DevOps Pipelines tab, and select your pipeline.
Click the down arrow icon under Approved Work Items, and then select
Replace Environment.
Review the considerations, select the confirmation checkbox, and then click
Continue.
Select an environment, and then click Log In.
Complete the login process.
DevOps Center replaces the environment. Check whether the development environment is
out of sync. If it is, sync it before you continue work. See Keep Your Development Environment in Sync.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
