QC Storage Bridge Entitlement Revalidation Scheduled Task

This article documents the canonical 60-minute entitlement security boundary, what invalid/missing/disabled/too-slow task state means for effective premium access, and why normal frontend requests do not perform remote entitlement calls.

What you need to know

• The canonical task cadences are: Entitlement Revalidation 60 minutes, Transfer Continuation 5 minutes, Recovery Vault Cleanup 60 minutes, and Notification Delivery 5 minutes.

Security-canonical behavior

• Canonical cadence: every 60 minutes.
• A missing, disabled, duplicate, structurally invalid, or slower-than-hourly canonical task forces above-Basic effective use back to Basic instead of allowing stale premium access indefinitely.
• Temporary communication-failure continuity is bounded (current logic uses a maximum 24-hour grace window) and never extends beyond a known paid/preview expiration.
• The background task revalidates existing entitlement state; it must not start an untouched Max Preview automatically.
• Frontend rendering remains local/read-only rather than performing remote entitlement HTTP work on normal page loads.

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.

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.

Troubleshooting

• On a quiet site, use server cron for Joomla scheduler:run --all rather than assuming Lazy Scheduler will run on time.

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.