Skip to main content
The CLI reads the workspace upload policy before transferring files. With sessions enabled, source-only groups use resumable upload sessions. Groups retaining conversions use a single multipart bundle through the ordinary upload route.

Resume a source-only import

After an interrupted run, repeat the same command with unchanged inputs and destination. The client hashes file content and derives stable upload keys from the destination, group identity, filenames, content and roles. An existing session skips accepted parts or returns the completed entry. A changed group can form a different operation, so inspect the plan again after editing local files or the manifest. Within each file, parts are sent sequentially. --concurrency controls simultaneous group transfers, defaults to 2, and accepts 1–8. Choose the value in conjunction with the server’s limits and available bandwidth.

Prefer direct S3 multipart

The server must enable direct multipart, and the workspace must use an eligible private S3 disk. The file must meet the threshold. The returned transport determines the actual path. Each direct part is hashed, signed, uploaded to storage and acknowledged using its ETag. Studio verifies the assembled file before publishing it.

Check limits before retrying

For a bundle that exceeds the ordinary limit, use rebuild mode if you want Studio to regenerate conversions, or adjust the application’s ordinary upload policy and ingress. Keep mode retains its bundle transport even when --direct is supplied. The client retries transient network failures and HTTP 429, 502, 503 and 504 up to three times after the initial attempt. Each HTTP attempt has a 120-second timeout. Integer Retry-After delays are capped at 60 seconds. A permanent validation or permission failure needs a configuration or input correction. Upload recovery and cleanup