spec.json and Sync Frequency
Why This Matters
Many engineers assume spec.json controls sync frequency — it doesn't. Clearing this misconception early prevents incorrect configuration attempts and wasted debugging time.
What You'll Learn
- What spec.json is: a per-integration metadata file consumed by the integrations dashboard, not the SyncApp
- Why every integration has its own spec.json (Weave supports 90+ PMSs, no global spec possible)
- What fields spec.json contains: integration name, version, sync frequency, entity list, etc.
- The critical fact: SyncApp business logic does NOT read spec.json — including sync frequency in minutes
- What the integrations dashboard uses spec.json for
- Where sync frequency is actually controlled (teaser for the next lesson)
Watch Video
Lesson Summary
spec.json is a metadata file that exists per-integration in the SyncApp repo. With 90+ PMS integrations, each is too different for a global configuration file. spec.json contains integration name, version, sync frequency in minutes, entity list, and other metadata. However — crucially — none of this is read by SyncApp's business logic. The SyncApp does not use spec.json's sync frequency to decide how often to sync. spec.json is consumed by the integrations dashboard to display integration metadata. Actual sync frequency control in SyncApp uses a different mechanism: Schedulers.