Check the status of a sandbox creation, and log in to it if it’s ready.
Description for org resume sandbox
Sandbox creation can take a long time. If the original “sf org create sandbox” command either times out, or you specified the –async flag, the command displays a job ID. Use this job ID to check whether the sandbox creation is complete, and if it is, the command then logs into it.
You can also use the sandbox name to check the status or the –use-most-recent flag to use the job ID of the most recent sandbox creation.
Aliases for org resume sandbox
env:resume:sandbox
Flags
Flag Name (Long)
Flag Name (Short)
Description
‑‑flags‑dir
N/A
Type: Value
Import flag values from a directory.
‑‑job‑id
‑i
Type: Value
Job ID of the incomplete sandbox creation that you want to check the status of.
The job ID is valid for 24 hours after you start the sandbox creation.
‑‑json
N/A
Type: Boolean
Format output as json.
‑‑name
‑n
Type: Value
Name of the sandbox org.
‑‑target‑org
‑o
Type: Value
Username or alias of the production org that contains the sandbox license.
When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to the new sandbox org.
‑‑use‑most‑recent
‑l
Type: Boolean
Use the most recent sandbox create request.
‑‑wait
‑w
Type: Value
Number of minutes to wait for the sandbox org to be ready.
If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume checking the sandbox creation, rerun this command.
Examples for org resume sandbox
Check the status of a sandbox creation using its name and specify a production org with alias “prodOrg”:
j