`sf org create sandbox --source-sandbox-name` fails when cloning org with Sandbox Data Storage Upgrades

[soileaud]

Summary

Cloning developer sandboxes that use the upgraded 400MB storage feature from the cli fails with Invalid Inputs: You must specify the Features that were added to the sandbox being cloned.

Steps To Reproduce

• Create a sandbox using the 400MB upgrade
• Optional: Confirm feature value using tooling api query SELECT SandboxName, Id, Features FROM SandboxInfo --> Should be ["SandboxStorage"]
• Run command sf org create sandbox --target-org PROD --name newSandBoxName --source-sandbox-name oldSandoxName

Expected result

Sandbox creation should be queued in prod org as a clone of source sandbox

Actual result

Error (1): Invalid Inputs: You must specify the Features that were added to the sandbox being cloned.

Additional information

Would be nice if sandbox definition files supported including this feature for net new sandboxes, but even if that is added it should not be required when cloning.

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.88.6",
  "nodeVersion": "node-v22.15.0",
  "osVersion": "Darwin 24.4.0",
  "rootPath": "/Users/soileaud/.local/share/sf/client/2.88.6-85f5a40",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.28 (core)",
    "@oclif/plugin-commands 4.1.25 (core)",
    "@oclif/plugin-help 6.2.28 (core)",
    "@oclif/plugin-not-found 3.2.51 (core)",
    "@oclif/plugin-plugins 5.4.37 (core)",
    "@oclif/plugin-search 1.2.24 (core)",
    "@oclif/plugin-update 4.6.39 (core)",
    "@oclif/plugin-version 2.2.28 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.39 (core)",
    "@oclif/plugin-which 3.2.35 (core)",
    "@salesforce/cli 2.88.6 (core)",
    "apex 3.6.17 (core)",
    "api 1.3.3 (core)",
    "auth 3.6.118 (core)",
    "data 4.0.30 (core)",
    "deploy-retrieve 3.22.9 (core)",
    "info 3.4.59 (core)",
    "limits 3.3.53 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.7.5 (core)",
    "packaging 2.13.3 (user) published 5 days ago (Sat May 10 2025)",
    "schema 3.3.61 (core)",
    "settings 2.4.27 (core)",
    "sobject 1.4.55 (core)",
    "telemetry 3.6.40 (core)",
    "templates 56.3.46 (core)",
    "trust 3.7.87 (core)",
    "user 3.6.20 (core)",
    "sfdmu 4.38.0 (user) published 137 days ago (Sun Dec 29 2024)",
    "sfdx-browserforce-plugin 4.7.0 (user) published 57 days ago (Wed Mar 19 2025)",
    "sfdx-git-delta 6.7.0 (user) published 3 days ago (Mon May 12 2025)",
    "sfdx-hardis 5.34.1 (user) published 0 days ago (Thu May 15 2025)",
    "sfdx-plugin-source-read 1.5.1 (user) published 57 days ago (Wed Mar 19 2025)",
    "texei-sfdx-plugin 2.8.3 (user) published 66 days ago (Mon Mar 10 2025)"
  ]
}

[github-actions[bot]]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[github-actions[bot]]

Hello @soileaud :wave: None of the versions of sf you shared match the latest release.

Shared: 2.82.6 Latest: 2.88.6

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[shetzel]

Looks like that was added in the Winter 2025 release so this is a feature request.

[git2gus[bot]]

This issue has been linked to a new work item: W-18539941

[thomasminney]

@shetzel @soileaud is this now resolved?

Can this be made available using definition files? https://github.com/forcedotcom/cli/discussions/3286

[soridalac]

Hi @thomasminney, it has been resolved and also available via definition file.

Doc: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_sandbox_definition.htm PR: https://github.com/salesforcecli/plugin-org/pull/1443

[thomasminney]

Thanks @soridalac , I re-tested the definition file approach using "features": "['SandboxStorage']" and it now works, thank you.