Platform Outbox
Monitor and manage platform-level events that must reach downstream systems (CRM, analytics, notifications).
Last updated: 2026-01-26 Where to find it: Admin > Platform Outbox Who can use it: Admin roles with technical access Prerequisites: Admin access, technical understanding of event systems Help link: /admin/platform-outbox
Overview
Platform outbox entries are not tied to a specific club and are processed by the TeeTime outbox worker.
What you'll see (fields/columns)
Metrics
| Metric | Description |
|---|---|
| Pending | Events waiting to be processed |
| Processed | Successfully delivered events |
| Failed | Events that failed delivery |
| Dead-lettered | Events exceeding max retry attempts |
| Lag | Age of oldest pending event |
Entries List
| Column | Type | Description |
|---|---|---|
| ID | Text | Entry reference |
| Event Type | Badge | Type of event |
| Tenant | Text | Associated tenant |
| Status | Badge | Pending, Processed, Failed, Dead-lettered |
| Created | Timestamp | When event was created |
How to do it
Requeue Failed Entries
- Filter entries by Failed status.
- Review error details.
- Fix upstream issue if needed.
- Click Requeue to retry.
Bulk Requeue
- Filter by status or event type.
- Select entries to requeue.
- Click Bulk Requeue.
- Confirm the action.
Purge Old Entries
- Set retention window filter.
- Select processed entries to purge.
- Click Purge.
- Confirm deletion.
Screenshot / Callout
Expected outcome
- Events are delivered to downstream systems.
- Failed entries are investigated and requeued.
- Lag remains minimal during normal operations.
Troubleshooting
- Lag increasing? Check worker health and queue depth.
- Repeated failures? Inspect entry payload and error, then requeue after fix.
- Dead-lettered entries? Review error message and max attempts, then requeue if safe.