Manual downtime compensation

An administrator specifies the number of hours to add to active finite subscriptions. Deployment does not issue any compensation automatically.

Administrator workflow

Sign in to the website with an administrator account.
Open Downtime compensation.
Enter hours in quarter-hour steps (0.25–8760), a reason, and all active subscriptions or a list of usernames.
Select Review recipients. Check the exact accounts, current expiration dates, and hours.
Select Apply … hours to … accounts. The server rechecks administrator permission, CSRF, eligibility, and the five-minute preview.
Review the recorded event in history. Each event has an ID, administrator, reason, hours, timestamp, and recipient count.

What changes

Active Booster, Plus, and Pro subscriptions with finite future expiration dates are extended by the selected number of hours. Lifetime, expired, and missing-expiration accounts are excluded. There is no lifetime duration to extend.

The preview is bounded to 1000 recipients, or up to 200 explicitly selected usernames. Use separate batches for larger groups. Applying an event uses a transaction, row locks, and a unique request ID to prevent double application.

Active redeemed keys associated with eligible accounts receive equivalent credit, and existing key activations are extended. A key issued or redeemed later does not automatically inherit an older incident's compensation. Keys that had already expired are excluded. Redeeming a new key does not erase the account's longer existing expiration.

Access and limits

The page/API require a current verified administrator session. Account keys do not grant administrator access. Reasons and results are rendered as text. No password, cookie, or Roblox credential belongs in a compensation reason.

This is manual compensation, not an automatic outage detector or a promise of a fixed service level. No live compensation has been applied as part of implementation, and a real administrator transaction has not been exercised.