Daily Focus
Command Center
Operations cockpit for launches, risks, payouts, and daily execution.
Payment alert
Needs reviewChecking pending payments…
Database alert
Needs reviewChecking idle transactions…
Focus Mode
Sandbox RequiredAutomations run dry first, then require operator approval before live impact.
Guardrails on
Approval required for non-sandbox execution.
Manual checkpoints
Critical flows pause on payment and routing anomalies.
Audit trail
Module and ops changes are logged for review.
Today
2 Critical
4 Routine
Upcoming activities
Click a row to inspect details.| Title | Start | Price | Seats | Revenue | Status | Actions |
|---|
Activity control
Status, registrations, and split payouts.Selected activity
Details and payouts for the selected activity.
Select an activitySplit payouts
| Account | Razorpay ID | Share |
|---|---|---|
| No splits configured. | ||
Registrations
Registrations for the selected activity.
Add participant (free)
| Name | Phone | Qty | Amount | Status | Created | Actions |
|---|---|---|---|---|---|---|
| Select an activity. | ||||||
Revenue analysis
Range-based performance, payouts, and trend signals.
Revenue range
Select a range.
Active Revenue
₹0
Tickets Sold
0
Active Registrations
0
Refunded Revenue
₹0
Refunded Registrations
0
Repeat Participation Rate
—
Last 30 completed calendar days.
Payouts & settlements
| Account | Settled | Pending |
|---|---|---|
| Loading… | ||
Revenue timeline
Trend view for the selected range.
Created range
Filter by created date for quick audits.
Created activities
Click a row to inspect full status.
| Title | Community | Kind | Status | Start | Created | Participants |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Activity status
Full status for the selected activity.
Select an activity
Status
—
Kind
—
Community
—
Participants
0
Created
—
Expires
—
User insights
Repeat, spend, and cohort breakdowns.
Active users
0
Total users
0
Repeat users
0
Tickets sold
0
Total spend
₹0
Revenue per user
₹0
Revenue per ticket
₹0
Top category (revenue)
—
No category data.
Top category (attendance)
—
No category data.
Top category (users)
—
No category data.
Top attendees
| Name | Phone | Activities | Tickets | Spend | Top category | Last |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Top spenders
| Name | Phone | Activities | Tickets | Spend | Top category | Last |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Category affinity
| Category | Users | Attendances | Tickets | Spend | Last |
|---|---|---|---|---|---|
| Loading… | |||||
Monthly reward suggestions
Retention-focused suggestions for new, growing, and loyal regulars. Two slots prioritize players without a recent monthly reward; one keeps space for sustained loyalty.
| City | Topic | Suggestion | Player | Behaviour | Discount history | Reward % | Status | Action |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
Discount grants
Apply one-ticket percentage discounts to specific users.
Active grants
| User | Phone | Percent | Uses | Activity | Expires | Status | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Support
Support tickets created from the mobile profile activity log appear here with the linked activity and refund context. Click a ticket row to open the expanded detail view.
| Created | User | Activity | Issue | Refund | Status |
|---|---|---|---|---|---|
| Loading… | |||||
Recurring schedules
Manage recurring activity templates and schedules.
| Name | Days | Status | Next | Actions |
|---|---|---|---|---|
| Loading… | ||||
Recurring detail
Loading detailManage the selected recurring schedule.
Select a scheduleUpcoming instances
Recent history
Service health
Lightweight heartbeats from background workers.
Server time
—
Recurrence sweeps
—
Activity counters
—
Resilience
—
Recurrence worker
Sweep heartbeat + DB signals.
Last OK
—
Last fail
—
Message
—
Active recurrences
—
Last generated
—
Last instance created
—
Resilience queues
DB-wide current state; no payloads or provider calls.| Component | Status | Due / age | Stale / age | Failed / terminal | Reason |
|---|
Critical consumers
Liveness and cycle heartbeats; liveness does not prove progress.| Component | Status | Heartbeat age | Last OK | Reason |
|---|
Provider reconciliation
——
Last cycle
—
Budget
—
Due / stale
—
Retrying / unresolved provider
—
Redis failures
—Actual command failures in this process since start; current status uses a 15-minute recency window and collection never calls Redis.
Timeout / other
—
Fail-closed / best-effort / unclassified
—
Policy failure ages (same order)
—
Last failure
—
DB connection pool
—Connection utilization for this API process. Alert threshold: ≥80%; exhaustion affects current status for 15 minutes.
Used / Max
—
Utilization
—
Free connections
—
Exhaustions since process start
—
Last exhaustion
—
Slow queries
—Queries exceeding the slow query threshold since last restart. Newest first.
| Time | ms | Query | Request ID |
|---|
Activity counter drift
Seat counter mismatch between cached activity values and canonical participants.
Drifted activities
—
Last drift seen
—
Sample
—