Best Practices for Cloning On-Demand Sandboxes
Follow these recommendations to optimize your sandbox cloning workflow.
| Best Practice | Description |
|---|---|
| Choose Appropriate Resource Profiles | Select the profile that meets your requirements. For cloning, the target profile should be the same size or larger than the source sandbox profile. |
| Review Custom Configurations | After cloning completes, test all integrations and custom configurations. Update third-party endpoints, keystores, and Business Manager customizations that reference the source sandbox. |
| Manage Cloned Sandboxes | Delete cloned sandboxes when no longer needed to reduce credit consumption. |
| Plan Clone Operations | Where feasible, execute large clone operations during times when sandbox usage is low. |
| Save Your Work | During the clone process, the source sandbox is stopped. Make sure to save any open work before triggering the clone operation. |
| Monitor Clone Progress | Monitor the progress of a clone using the Monitor Clone Progress API. Poll the API every 30–60 seconds to check status, but avoid excessive polling, which can trigger rate limits. |
| Set Time-to-Live Values | Configure the TTL parameter to automatically clean up temporary clones and avoid consuming unnecessary credits. |