Immediate-First Transfer Processing
This article explains that QCSB attempts useful work immediately after submission for responsive UX and leaves unfinished eligible work for scheduled continuation rather than making users wait for an entirely background-only process.
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.
What immediate-first means
| Stage | Behavior |
|---|---|
| Initial request | QCSB starts eligible copy/move work immediately so normal/small transfers can finish without waiting for cron. |
| Unfinished work | Durable job/item state records what remains rather than forcing the browser request to run indefinitely. |
| Pro+ continuation | The canonical 5-minute Transfer Continuation task resumes eligible unfinished work. |
| Basic boundary | Do not describe Basic as having Pro background continuation; ordinary actions still attempt immediate work within the current request/capability. |
| Permission change | Continuation rechecks the original user’s current authority instead of treating submission-time permission as permanent. |
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.