Service status
0 of 5 configuredWhat is configured, and what that affects
Clutchhall reads its own configuration and reports it here. Each service says what stops working while it is unconfigured, and names the settings that are missing — names only, never values.
How to read this room
This is a configuration report, not a health check. Clutchhall has not called these services to see whether they answer, so “configured” means the deployment holds a real value for every setting the service needs — nothing stronger. Clutchhall does not claim a service is operational on the strength of a present setting.
A placeholder is not a value. Every setting in this deployment currently begins with a marker rather than a secret, which is why a service can be present in the configuration and still report as unconfigured here.
- Services
- 05
- Configured
- 00
- Blocking the app
- 01
- Awaiting settings
- 04
Services
05 trackedCommunity database
MissingWhat stops working without itAccounts, halls, competitions, and selections cannot be read or written.
Required before any signed-in room can show real data.
Missing settings (1)- SUPABASE_SECRET_KEY
Season subscription
Not configuredWhat stops working without itA community cannot start or change a season subscription, and entitlement cannot be verified.
Not required to serve a signed-in room; the feature it powers is unavailable without it.
Missing settings (4)- STRIPE_SECRET_KEY
- NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY
- STRIPE_COMMUNITY_PRICE_ID
- STRIPE_WEBHOOK_SECRET
Schedule and results feed
Not configuredWhat stops working without itAuthoritative kickoff times and official results are unavailable, so locks and scoring cannot run.
Not required to serve a signed-in room; the feature it powers is unavailable without it.
Missing settings (3)- SPORTS_DATA_PROVIDER
- SPORTS_DATA_API_BASE_URL
- SPORTS_DATA_API_KEY
Transactional email
Not configuredWhat stops working without itInvitations, receipts, and correction notices cannot be delivered.
Not required to serve a signed-in room; the feature it powers is unavailable without it.
Missing settings (1)- EMAIL_FROM
Web push
Not configuredWhat stops working without itDeadline reminders cannot be delivered to a device.
Not required to serve a signed-in room; the feature it powers is unavailable without it.
Missing settings (3)- NEXT_PUBLIC_WEB_PUSH_VAPID_PUBLIC_KEY
- WEB_PUSH_VAPID_PRIVATE_KEY
- WEB_PUSH_SUBJECT
Setting names are listed so an operator can see what is left to do. No value, key, token, or URL is ever rendered on this page.
During an incident
Availability work and support effort are prioritised around lock windows and scoring runs, because those are the moments where an outage costs a community something it cannot get back.
- An outage response says what will happen
- Not what should have happened. If a lock window is affected, the response states plainly what will be done with the affected round before anything is scored.
- No retroactive selections, ever
- Clutchhall does not accept a selection after its lock, reconstruct one from a device draft, or infer one from a participant’s history. A round with no valid pre-lock receipt scores as it stands.
- A delayed kickoff does not reopen a lock
- This holds during an incident too. The lock followed the authoritative kickoff time, and an incident does not move it.
- Scoring holds rather than guesses
- If the results feed conflicts with itself, the round is held provisional and resolved against the designated source-of-truth policy. The more convenient result is not chosen.
- A correction is the only route back
- Anything an incident got wrong is fixed through the append-only correction process, with actor, time, reason, evidence, and before-and-after values, and with materially affected participants notified.