Reading the sync status dashboard

For: An ops lead or admin doing a health check on their PropSocket data.

You’ll accomplish: understanding what each sync status means in plain terms, knowing how fresh your data should be, and finding the per-data-type breakdown when you need detail.

A sync is one run where PropSocket fetches the latest from your PMS (like Entrata) and updates its copy. There are two places you’ll check on syncs:

• Sync Monitor — a single page listing every sync run across all your integrations, with filters. Good for “show me what’s run lately, and did anything fail?”
• An integration’s own pages — the integration list and detail views, which show that one connection’s health, freshness, and recent runs.

And there are two kinds of status worth telling apart up front:

• Integration status — the overall health of a connection (is it on, syncing right now, broken, or turned off?).
• Sync job status — how one individual sync run turned out.

This guide covers both.

---

1. What the integration status means

On the integration list and on each integration’s detail header, every connection shows an overall status badge:

• Active — Connected and on schedule. Nothing to do.
• Syncing — A sync is running right now. Normal; it’ll settle back to active when it finishes.
• Error — The most recent attempt didn’t succeed. Your data is still there and usable, but it hasn’t updated since the last good run. See What to do when a sync fails.
• Disabled — The integration is turned off and isn’t syncing. Someone paused or disabled it on purpose. (The detail header’s Resume button turns it back on.)

The integration’s Overview tab adds a plain-language health label next to a colored dot:

• Healthy — running cleanly (often with a “N consecutive successes” count).
• Degraded — running, but some properties or recent runs are having trouble.
• Failing — needs attention.

If you manage many properties on one integration, the Property Health bar breaks this down further — how many individual properties are healthy, degraded, or failing.

2. What each sync job status means

In the Sync Monitor (and in an integration’s Recent Syncs list), each run shows one of four statuses:

• Pending — Queued and waiting to start. No action needed.
• Running — Actively pulling data from your PMS right now.
• Completed — Finished successfully. Your data is current as of this run’s time.
• Failed — This run didn’t finish. Important: your existing data is not lost or wrong — it’s simply as fresh as the last completed run, not this failed one.

A single failed run is not an emergency on its own. What matters is your last completed sync (next section).

The Sync Monitor also lets you filter the list by integration, status, tag, and type (Initial vs. Ongoing — see section 4), and shows at-a-glance cards for the last 24 hours: Total Syncs, Success Rate, Avg Duration, and Failed.

3. Judging how fresh your data is

This is the question most health checks come down to: how current is my data right now?

On the integration list card and the Overview tab, you’ll see a single Last sync time paired with a status indicator (OK, Failed, or Running). Read them together:

• Last sync = OK → that time is when your data was last refreshed. You’re current as of then.
• Last sync = Failed → that time is when PropSocket last tried, not when it last succeeded. Your data is actually as fresh as the most recent Completed run before it.

Example: if the Last sync shows “30 minutes ago” but the status is Failed, your data is not 30 minutes old. To find out how fresh it really is, open Recent Syncs (or the Sync Monitor, filtered to that integration and status Completed) and look at the most recent Completed run — that run’s time is your true data freshness.

In short: when the latest run failed, don’t trust the “Last sync” time as your freshness. Find the most recent Completed run instead.

4. How often syncs should run (expected cadence)

The first run on a new integration is an Initial sync (a one-time full load). Every run after that is an Ongoing sync, on a schedule that depends on your plan:

Plan	Sync cadence
Starter	Every 4 hours
Growth	Customizable, as often as every 15 minutes
Scale	Customizable, as often as every 5 minutes
Enterprise	Customizable

So on Starter, seeing your last completed sync within the past 4 hours is healthy. The Overview tab also shows a Next sync time so you know when the next scheduled run is due. If the gap since your last completed sync is much larger than your cadence — or Next sync has come and gone with nothing new — something’s likely wrong; check the run statuses and see What to do when a sync fails.

You can also trigger a sync any time you need fresher data right now, rather than waiting for the next scheduled run: use the Sync Now button on the integration’s detail page (or the Sync button on its card).

5. See the per-data-type breakdown

Click any run to open its detail page. There you’ll find:

• Models Synced — which data types the run touched (properties, units, residents, leases).
• A Record Counts table — how many records were created, updated, and deleted, broken out per data type with a total row.

This is the fastest way to sanity-check a run. For example, if you onboarded 200 new units in Entrata yesterday but the latest run’s Record Counts show zero units created, that’s a signal worth investigating in What if our data looks wrong?.

The run detail page also has an Execution Logs section — a timestamped log of what happened during the run, filterable by Info / Warning / Error and labeled by model and property. If a run failed or a count looks off, this is where the why usually is. Failed runs also surface an Errors panel with the failure message at the top of the page.

A note on “deleted”: When a record disappears from your PMS, PropSocket marks it as deleted rather than erasing it. It’s hidden from your normal views but kept for your records. So a count of deleted records usually just means those items were removed in Entrata.

---

If this didn’t work

If a status doesn’t make sense, syncs have stopped, or the freshness doesn’t match what you expect, we’ll help you read it.

Open a support ticket by emailing support@propsocket.io and include:

• Organization slug (the short name in your dashboard URL, e.g. acme-residential)
• Integration name (and the link to its detail page, if you have it)
• The link to the specific sync run (the run’s detail-page URL) if you’re asking about one run
• The time window you’re looking at (e.g., “syncs between 6am and noon ET today”)
• What you expected vs. what you saw
• A screenshot of the Sync Monitor or the run’s detail page

You don’t need to send any data records or credentials — the links and names above are enough for us to find the run.