QCSB Transfer Completion and Failure Notifications

This article explains the current customer-visible notification path for completed/failed durable transfers, Joomla Mail dependency, safe details, and where delivery outcome is recorded.

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.
  • Transfer completion/failure events are persisted to a durable outbox and delivered through Joomla Mail by the 5-minute Notification Delivery task.
  • QCSB 1.01.08 does not expose a customer Email Templates tab. Internal responsive templates/delivery state are maintained by the service and upgrades preserve genuine stored customizations.

Delivery path

  1. A transfer reaches a terminal state such as completed, completed with warnings, failed, or cancelled.
  2. QCSB persists the corresponding notification event to its durable outbox.
  3. The QC Storage Bridge Notification Delivery Scheduled Task processes pending delivery every 5 minutes.
  4. The service renders the internal responsive template and sends through Joomla Mail.
  5. Delivery outcome/retry state is stored so a temporary mail failure does not require the transfer itself to be repeated.

Verify the result

  • Status shows the canonical task as healthy and published.
  • The cadence matches the current required interval.
  • A manual/next scheduled run finishes without a repeated non-zero exit state.

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.