Move a fix to a sandbox
Made an urgent configuration change straight in production? Capture it as a change set and carry it back down to your sandboxes so they stay in sync.
Most changes start in a sandbox and travel up toward production. But a fix sometimes has to happen directly in a production environment. When it does, your sandboxes fall behind. Change sets can move in any direction, so you can capture that fix and bring it back down.
Capture the fix
- Open a production environment and choose Review so Mochi reads its current configuration.
- Select the items you changed in production, then choose Review & create change set.
- Describe it and choose Pull in as a change set. Mochi gathers the items and anything they depend on, so the fix is captured as a proper, reviewable change set. From a production environment the button says “pull in” rather than “create” because the change is already live there. It behaves like any other change set.
Carry it down to your sandboxes
Once the fix is part of your configuration, it travels like any other change set: run the pipeline. The run enters at the earliest stage that's behind, which is the sandbox that needs the fix, and moves along from there. Deliveries follow the pipeline in order rather than jumping to a single environment, so everything in between catches up too. See Run a pipeline for the steps.