How QCSB Turns Copy and Move Operations into Durable Transfer Jobs

This article explains job and item tracking for multi-step file operations so transfers have durable state, progress, retry information, and history instead of depending on a single browser request.

What you need to know

  • Copy/Move authorization is directional: QCSB checks the source-side permission and the destination-side permission independently.
  • Move is destructive only after the destination has been written and verified; the source is Recovery-protected before removal.
  • 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.

Job creation flow

  1. The user selects source items and a permitted destination, chooses Copy or Move, and confirms conflict handling.
  2. QCSB rechecks source/destination permission and creates durable job/item state before relying on a long browser request.
  3. QCSB immediately attempts ordinary work in the initiating request—the model is immediate-first, not “queue everything and wait.”
  4. If eligible Pro+ work remains unfinished, the 5-minute Transfer Continuation task can resume it later.
  5. Each item records its own result so successful items are not undone merely because another item failed or was cancelled.

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.

Important limits and mistakes to avoid

  • Do not bypass failed recovery protection to force a destructive action. The block is intentional safety behavior.

Troubleshooting

  • If a file action fails, retry with one small test item and read Transfer Details or the operation toast before changing global settings.

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.