Academy / Sync App Flow & Deployment / SyncApp Flow and Entity Schedulers

SyncApp Flow and Entity Schedulers

Lesson 5.1 ⏱ ~8 min

💡 Why This Matters

Entity schedulers are how SyncApp balances thoroughness with efficiency. Understanding how to configure per-entity cron jobs is a core skill when building new PMS integrations.

🎯 What You'll Learn

  • What an 'entity' is in SyncApp: patients, appointments, providers/practitioners, recalls, accounts, orders, pets
  • How each entity has its own independent scheduler/cron job within SyncApp
  • How SyncApp decides whether to do a full or partial sync for each entity in each cycle
  • Why common entities (patients, appointments) default to 15-minute cron jobs
  • Why non-common entities (orders, accounts) have no default cron and must be configured when building new integrations

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

SyncApp processes each entity type (patients, appointments, providers, recalls, accounts, orders, pets) independently. Each entity has its own cron job/scheduler, configurable independently of the others. On each 15-minute cycle, SyncApp checks each entity's scheduler to determine if it's time to sync that entity. Common entities like patients and appointments have a 15-minute default schedule. Less frequently changing entities like practitioners can be set to 24-hour schedules. When building a new integration, non-common entities have no default cron job — you must configure one.

🏷 Key Concepts

Entity Types Per-Entity Cron Job Scheduler 15-Minute Default Cycle Full vs Partial Decision Point Configurable Sync Frequency New Integration Setup

Key Takeaways

01Each entity has its own cron — don't assume all entities sync at the same frequency
02When you build a new integration, you must explicitly configure cron jobs for non-common entities
03The 15-minute 'SyncApp cycle' is the outer loop; individual entity crons are the inner decision
04Practitioner data changes infrequently — syncing it every 24 hours is sufficient and reduces PMS API load
05Appointment data changes frequently — 15-minute or shorter schedules are appropriate

🔗 References & Resources

📎 Additional Materials for This Lesson

⚠️ Update: Port forwarding for the Deploy UI is no longer required. Use the direct links below.