Welcome, Customer
View and manage your support tickets
Open Tickets
0
In Progress
0
Resolved
0
Search Knowledge Base
Popular Articles
Hub & Spoke Model
The Hub is the central database storing authoritative data. Five Spokes (Path, HealthFlow, Continuum, Vitalis, Money) connect to the Hub. Data flow: User makes change in spoke → recorded in Hub → broadcast to all other spokes → reconciliation verification. Bidirectional sync allows data to flow Hub→Spoke (push) and Spoke→Hub (pull).
Spoke Goes Offline
Immediate actions: (1) Check spoke API health endpoint, (2) Verify network connectivity, (3) Check for recent deployments, (4) Review auth token validity. System response: Auto-queues syncs in SyncQueue table, retries exponentially for 24 hours, escalates after 24 hours. Check SyncFailureAlert table for logged issues.
How do I manually trigger a sync?
Admin Dashboard → Network Status → Select spoke → Click 'Sync Now'. Use force sync only for troubleshooting. Normal sync is automatic and handles queuing/retries.
What does 'newest wins' mean?
If the same field is updated in two spokes simultaneously, the most recent update (by timestamp) is kept across all systems. Prevents data loss but overwrites the earlier change.
Path (Life Planning)
Purpose: Life planning, legacy planning, estate management. Features: Create life plans, document legacy wishes, manage digital estate, timeline tracking. Data synced: User profiles, life plans, legacy documents, care preferences. Support tip: Check last sync timestamp in sync status if data doesn't appear elsewhere.