Handle errors and updates
Read the command’s message. The request ID appears in --json output, so use --json in scripts and keep the request ID when asking for help. Before running a write again only to see its request ID, check whether the first attempt was accepted. The CLI exits with a status that scripts can use without matching message text.
| Status | Meaning | Next step |
|---|---|---|
| 0 | Success | Use the returned result. |
| 1 | Another local, network, or processing failure | Read the message and check the connection or local file. |
| 2 | Invalid command or input | Check the command’s --help and correct the input. |
| 3 | Sign-in required | Run flashdrive login, then check whoami. |
| 4 | Permission refused | Check your account, selected drive, and granted actions. |
| 5 | Resource not found | Check the ID and selected workspace or drive. |
| 6 | Conflict or a changed revision | Read the current version and reconcile the change. |
| 7 | Rate limited | Follow the retry advice in the response. |
| 8 | Payment or credits required | Review Billing in the Console. |
| 9 | Capacity or quota reached | Review the displayed limits and current usage. |
| 10 | Service temporarily unavailable | Follow the retry advice and retain the request ID. |
| 11 | Client update required | Update the CLI before retrying. |
| 12 | Waiting timed out | Check the accepted operation or upload; do not assume it failed. |
| 130 | Interrupted with Ctrl+C | Check accepted work before running the command again. |
Check accepted work
flashdrive upload status UPLOAD_ID
flashdrive operation status OPERATION_ID --waitUse the ID the command returned and the original drive. A timeout of the waiting command does not cancel accepted service work.
Update the client
flashdrive update --check
flashdrive update
flashdrive --versionThe update command uses the install method associated with the CLI. Keep any unsaved mounted work and check flashdrive mounts after an update or restart.
Use in a script
flashdrive --drive DRIVE_ID file list --json--json returns structured output. Check the process status as well as the result. Retry a write only according to its returned advice and idempotency requirements; a response lost after acceptance is not permission to create the same content twice.