Is your integration healthy? A two-minute self-check

For: An ops lead doing a routine check, or anyone who’s been asked “is the PropSocket integration okay?” and wants a confident answer.

You’ll accomplish: running through a short checklist that tells you whether your integration is healthy, watching, or needs action — and where to go for each outcome.

You don’t need to wait for something to break to check on an integration. This is the same handful of signals a customer success manager would look at. Run it once a week, or any time someone asks.

You don’t need to write any code for this.

---

The checklist

The integration’s Overview tab already shows an at-a-glance health label — a colored dot reading Healthy, Degraded, or Failing (often with a “N consecutive successes” count). This checklist confirms that label and tells you what to do about each signal behind it.

Open the integration and answer these in order.

1. Is the integration status “active”?

• Active → good, move on.
• Syncing → also fine; a run is in progress. Check back shortly.
• Error → needs action. Go to What to do when a sync fails.
• Disabled → it’s paused on purpose. If that’s intentional, fine. If not, see Pause, resume, or remove an integration to resume it.

2. Is the last successful sync recent?

On the Overview tab, find the Last sync time — and read it together with the run’s status. If the last run failed, that time is the last attempt, not the last success; find the most recent Completed run instead (see Reading the sync status dashboard).

Compare that to your plan’s sync cadence — the Overview tab also shows a Next sync time so you know when the next run is due:

Plan	Sync cadence	“Recent” means within…
Starter	Every 4 hours	the last 4 hours
Growth	As often as every 15 minutes	your configured interval
Scale	As often as every 5 minutes	your configured interval
Enterprise	Customizable	your configured interval

• Within the window → healthy.
• Much older than the window → something’s wrong. Check the recent run statuses and go to What to do when a sync fails.

3. Are recent sync runs completing?

Open the sync history and look at the last few runs.

• Mostly completed, maybe one stray failure that the next run recovered → healthy. PropSocket retries automatically, so an occasional failure isn’t an emergency.
• A run of failures in a row → needs action. What to do when a sync fails.

4. Do the record counts look sane?

The Recent Syncs list (and the Sync History tab) show Records Created, Records Updated, and Records Deleted for each run. For a per-data-type breakdown, click a run to open its Record Counts table.

• Counts roughly match what changed in your PMS → healthy.
• Zero changes when you know there were big changes (e.g., you onboarded 200 units yesterday and see zero units created) → investigate with What if our data looks wrong?.

5. Are webhooks delivering (if you use them)?

Skip this if you don’t use webhooks. If you do, open the delivery log.

• Recent deliveries show “delivered” → healthy.
• Failures or dead-letters piling up → see Read your webhook delivery log.

---

Scoring it

• All five green → your integration is healthy. Nothing to do. You can tell whoever asked, with confidence, that data is current and flowing.
• One or two yellows (a stray failure, a slightly stale sync that’s catching up) → worth a glance, usually self-resolving. Note it and check again later.
• Any red (error status, a run of failures, stale data, missing changes, piling-up webhook failures) → follow the linked article for that signal. Most reds are fixable in a few minutes.

Before you assume an outage is on your side: check the status page — propsocket.statuspage.io. If we’re reporting an incident, several of these signals can go red at once through no fault of your setup, and there’s nothing to fix on your end.

---

If this didn’t work

If the signals contradict each other, or everything looks green but your data still seems wrong, send us what you’re seeing.

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)
• Which of the five checks looks wrong and what you saw
• What you expected vs. what you saw
• A screenshot of the integration overview

You don’t need to send any data records or credentials — the integration ID and which check failed are enough for us to start.