Sync Command Center — monitor and retrigger cross-platform sync
Goal: See the health and run history of every sync channel between Build and Match, and manually retrigger channels when needed.
Who can do this: Platform admins only.
Before you start: You need an active platform-admin session on Build.
Steps
- In the Build sidebar, click Sync command center.
- The page loads three panel groups:
- Automated sync channels — one card per cron channel (1, 2, 4, 7, 8).
- Admin-triggered sync channels — run log tables for per-template sync (3), template import (5), and assessment deploy (6).
- Entity links health and Identity links — derived metrics for channels 9 and 10.
Reading a cron channel card
Each card shows:
| Field | Meaning |
|---|---|
| Badge colour | Green = healthy, amber = warning, red = error. See thresholds below. |
| Last run | Relative time (hover for ISO timestamp). "Never" if no run has been recorded yet. |
| Records processed | How many items were synced in the last run. |
| Duration | How long the last run took. |
| Error | The last run error message, truncated to 120 characters. Expand to see the full text. |
The Question sync B→M card also shows the on-approval queue depth below the last-run row — pending and failed count for question-type events in the platform sync queue.
Health badge thresholds
| Channel type | Healthy | Warning | Error |
|---|---|---|---|
| Nightly crons (channels 1, 2, 4, 8) | Last run within 26 h, no error | Last run 26–48 h ago, or no run recorded | Last run had an error, or last run > 48 h ago |
| Event queue (channel 7, every 2 min) | Last run within 5 min, no error | Last run 5–15 min ago | Last run had an error, or last run > 15 min ago, or DLQ entries exist |
Reading an admin-triggered run log table
Columns: Entity name → Triggered at → Result (success / error) → Records in → Records out.
Pagination is 20 rows per page, newest first.
Retriggering a channel (platform admins only)
Two channels have a Re-trigger button:
- Session ingest (event queue) — drains the platform_sync_queue immediately instead of waiting for the next 2-minute cron tick.
- Session import (nightly) — runs the disassembly job that pulls completed sessions from Match into the Build data center.
Click Re-trigger and wait for the button to return to its idle state. The card data refreshes automatically after a successful retrigger.
What happens next
The page does not auto-refresh. Reload it to see updated status after a sync window has passed.
If a channel is still showing Error after a retrigger, copy the error message from the card and escalate to #producttech_cooking with the channel name and the error text.