Read QCSB Entitlement Health on the Status Tab

This article explains how to interpret Base/Effective tier, domain, verification mode, access dates, preview state, Legacy License Key state, last/next validation and task integrity.

What you need to know

  • Status separates entitlement, installation/runtime, connector readiness, task integrity, and extension-update health so a provider problem is not confused with a licensing or scheduler problem.

Read these fields together

Status fieldHow to interpret it
Base tierThe underlying purchased/base product entitlement.
Effective tierThe capabilities QCSB may use now after Base tier, All Access, or an active Max Preview is resolved.
Verification / DomainWhether current Authorized-Domain verification is healthy for the normalized domain.
Preview / access datesKnown server-authoritative limits that bound temporary/purchased premium access.
Legacy License KeyCompatibility/history only when an old saved key exists; not the current licensing workflow.
Last checked / Next automatic checkWhen entitlement was last confirmed and when the canonical hourly revalidation is expected again.

Do not read entitlement in isolation

Above-Basic use also depends on the canonical Entitlement Revalidation task remaining structurally healthy and running no slower than hourly. A provider failure is not automatically an entitlement failure; use the separate connector/readiness sections on Status to distinguish them.

Verify the result

  • Status shows the expected Base tier and Effective tier.
  • Verification/domain state is current and the hourly Entitlement Revalidation task is healthy.
  • Stored Workspaces/connections remain intact if Effective tier falls.

Important limits and mistakes to avoid

  • Do not reintroduce obsolete key-entry or short-preview instructions; 1.01.08 uses Authorized Domains and the explicit one-time 30-Day Max Preview.

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.