Open QCSB Transfer Details and Read Safe Per-Item Errors

This article shows how to inspect individual item outcomes and sanitized provider errors to identify the failing source/destination without exposing secrets or raw sensitive connector responses.

What you need to know

  • 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.

How to do it

  1. Expand Transfers in the frontend Workspace.
  2. Open Details for the affected job.
  3. Review each failed/retrying item by source name and the sanitized error message QCSB retained.
  4. Use the message to correct permissions, provider connectivity, destination conflict, or provider-state problems without exposing raw secrets.
  5. After correcting the cause, use Retry failed items; successful items are not intentionally repeated.

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.

Troubleshooting

  • Keep passwords, OAuth secrets/tokens, private keys, and unrestricted private paths out of public screenshots and support posts.

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.