Understand QCSB Transfer States, Item Counts, and Byte Progress
This article explains how to interpret queued/running/completed/warning/failed/cancelled outcomes, item counts, byte progress, and when a partially successful job still needs attention.
What you need to know
- Basic includes Local storage and the first active Workspace. Pro adds FTP/SFTP, multiple Workspaces, advanced permissions, and background continuation. Max/All Access adds Google Drive, OneDrive, Private Connections, Recovery Vault management, and bulk operations.
- A plan gate decides whether a feature exists at the current Effective tier. Joomla access and QCSB permission rules separately decide whether a particular user may use that feature.
- QCSB uses durable jobs but follows an immediate-first model: the request attempts ordinary work immediately, and only unfinished work remains for continuation.
- Pro/Max/All Access can use the 5-minute Transfer Continuation task. The worker rechecks the original user’s current authority before contacting a provider.
Current job states
| State | Meaning |
|---|---|
| queued | Durable job exists and eligible work has not finished yet. |
| running | A request/task is actively processing the job. |
| retry | Failed/eligible items have been placed back into retry processing. |
| cancelling | Cancellation was requested and QCSB is bringing active work to a safe stop. |
| completed | All required work finished successfully. |
| completed_with_warnings | The job finished but one or more items/results require attention. |
| failed | The job could not complete the required work. |
| cancelled | The job stopped after cancellation; items already completed are not rolled back automatically. |
Progress numbers
Item counts and byte progress are operational indicators for the durable job. Read them together with per-item Transfer Details: a job-level percentage alone cannot explain which particular item failed or why.
Verify the result
- The durable job reaches the expected terminal state: completed, completed with warnings, failed, or cancelled.
- Successful items remain successful; failed/retried items report their own sanitized outcome.
- For a Move, the source is removed only after the destination is verified and the source has required Recovery protection.
Community Discussion
For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.