Why did my Drive upload or file update fail?

These commands require the Drive CLI and an authorized session in the intended Socra Account.

Check the file size, destination, access level, and version used for the update. Drive rejects changes that would overwrite newer content or create an invalid path. Keep your local file while you resolve the failure.

Each file is limited to 16 MiB. Uploading requires writer or owner access, and the destination's parent must already be a folder in the same Drive. A reader can download but cannot upload.

A new file cannot use a name already taken by a live entry in that folder. Choose a new name, or update the existing file as a new version. Names cannot contain path separators or control characters; special names such as . and .. are invalid as entry names.

For a rejected content update, retrieve the file again:

socra drive file get FILE_ID

Compare its current version with the version you edited. If someone saved new content, download and review it before retrying. A rename or move also checks the entry's revision to prevent conflicting metadata changes.

If a download fails because its local destination already exists, choose a new output path. The CLI protects the existing file from overwriting. For a missing file, check your Account, grant, and whether the file or an ancestor folder is in trash.

If an upload loses its response, list the destination folder before retrying. The file may already have been saved. Download and inspect an existing result before deciding whether another upload is needed. A checksum error on download means the received content failed verification; the CLI does not create the output file. Retry to a new local path and verify the saved content.